Search results for "Postorius" - Mailman-users

Correct way to filter auto-replies to list?

by Stephen J. Turnbull

Gary Holman writes: > I have seen a few messages on this list regarding handling 'out of > office' auto-replies. However I do not see a final resolution. This problem is as hard as spam. There won't be a final resolution as long as people use out-of-office auto-replies. They're all different. If you are using a spam filter, I would suggest adding the offender's out of office message (or at least the spike protein :-) to your filter's body text blacklist. > What is the best practice to filter auto-replies to list: header > filter or postfix milter-reject or something else? You write "auto-replies" below. Set the subscriber to no-mail, or unsubscribe them for a second offense. Remind them that we put a huge amount of effort into creating and maintaining Postorius to make that as convenient as possible, and we at Mailman are "shock, SHOCKED, I tell you" that this courtesy was neglected. :-) > We are running dockerized Mailman 3 version 1.3.4. A list user > auto-replied their vacation message to list and then the listserv "listserv" is a trademark. Please don't use it to refer to Mailman. > created a chain-reaction of continuously replying to auto-replies > by that user. What do you mean by "chain reaction"? Other subscribers replying to the "out of office" message, or an auto-reply from the Mailman server? > There isn't really a good header option to filter > from, as the subject seems to be randomized. Vacation programs conforming to https://tools.ietf.org/html/rfc3834 https://tools.ietf.org/html/rfc5230 should provide some header fields to filter on. HTH, Steve

5 years, 1 month

Mailman issues after re-boot

by Paul Rubin

*<< I sent this to the mailman3 issues on gitlab and Mark replied but asked me to move to this list, so I copied everything and inserted responses. I hope this makes sense and someone can help me.>>* After a lengthy power failure I had to reboot a machine that has been running for several years. the WEB-UI does not seem to be able to see mailman-core. I have looked for log entries that might explain what the issue is and I am stumped to even find logs that will update when I get an error on the browser. Mailman is definitely running, postgres is running and mailman web is running. if I go to the lists page I see lists, if I try to access a specific list I get Server error: An error occurred while processing your request. I looked in /var/logs/mailman /opt/mailman/web/mailmanweb All I can find is: django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name.16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/goodstein.goodstein.org/ File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in <module> from django.utils.translation import ungettextImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/__init__.py) Also I have to run mailman from "mailman start" because the systemctl returns this: ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2023-09-12 10:06:31 EDT; 13s ago Process: 31159 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 806msSep 12 10:06:31 mail mailman[31159]: Error in atexit._run_exitfuncs:Sep 12 10:06:31 mail mailman[31159]: Traceback (most recent call last):Sep 12 10:06:31 mail mailman[31159]: File "/usr/lib64/python3.8/logging/__init__.py", line 2126, in shutdownSep 12 10:06:31 mail mailman[31159]: h.flush()Sep 12 10:06:31 mail mailman[31159]: File "/opt/mailman/venv/lib64/python3.8/site-packages/mailman/core/logging.py", line 67, in flushSep 12 10:06:31 mail mailman[31159]: if self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 10:06:31 mail systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURESep 12 10:06:31 mail systemd[1]: mailman3.service: Failed with result 'exit-code'.Sep 12 10:06:31 mail systemd[1]: Failed to start GNU Mailing List Manager. Please tell me where to start looking or adjusting. Reply from Mark Sapiro,* Edited to include responses:* Mark Sapiro <https://gitlab.com/msapiro>@msapiro <https://gitlab.com/msapiro>· 1 day ago <https://gitlab.com/mailman/mailman-web/-/issues/23#note_1557601916> Owner Add reaction More actions The mailman-users(a)mailman3.org list is probably a more appropriate place for issues like this. django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name. 16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/ goodstein.goodstein.org/ /opt/mailman/venv/lib64/python3.8/site-packages/postorius/urls.py should contain re_path( r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests', ), Y *Yes this exists* and /opt/mailman/venv/lib64/python3.8/site-packages/postorius/views/list.py should define list_unsubscription_requests. *Yes there is a method by this name defined* File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in from django.utils.translation import ungettext ImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/ *init*.py) See https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-re… - ungettext() is removed from django>=4.0 Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' I don't understand this one offhand, but what is the content of /etc/systemd/system/mailman3.service, in particular the settings for User, Group and ExecStart? *The service looks right:* 1 [Unit] 2 Description=GNU Mailing List Manager 3 After=syslog.target network.target postgresql.service 4 5 [Service] 6 Type=forking 7 PIDFile=/opt/mailman/mm/var/master.pid 8 User=mailman 9 Group=mailman 10 ExecStart=/opt/mailman/venv/bin/mailman start 11 ExecReload=/opt/mailman/venv/bin/mailman restart 12 ExecStop=/opt/mailman/venv/bin/mailman stop 13 14 [Install] 15 WantedBy=multi-user.target *It seems I may have two versions of the mailman script:* mail:/opt/mailman # which mailman /usr/bin/mailman mail:/opt/mailman # ls -al /usr/bin/mailman -rwxr-xr-x 1 root root 382 May 10 2021 /usr/bin/mailman mail:/opt/mailman # ls -al /opt/mailman/venv/bin/mailman -rwxr-xr-x 1 mailman mailman 231 Sep 12 10:02 /opt/mailman/venv/bin/mailman Somehow, your installation is corrupted. I don't know how *I need to know what to remove, how to correctly update, etc., That said the two scripts appear to be very similar:* mail:/opt/mailman # head /usr/bin/mailman #!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' __requires__ = 'mailman==3.3.4' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( mail:/opt/mailman # head /opt/mailman/venv/bin/mailman #!/opt/mailman/venv/bin/python3 # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) mail:/opt/mailman # *Given the two years since the last reboot I also tried following * https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was running the latest* pip install -U mailman postorius django-mailman3 hyperkitty mailman-web

2 years, 9 months

Re: Place holders

by Mark Sapiro

On 5/27/25 23:23, Mark wrote: > Hi, > > The place holders listed as available on the "Add new template" page are: > > $hyperkitty_url > $listname > $list_id: > $display_name > $short_listname: > $domain > $info > $request_email > $owner_email > $site_email > $language What Postorius version is this? You may be missing some things added in 1.3.11. A more complete list including the ones that only work in certain contexts is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… a pointer to which was added in 1.3.11. > The only one that seems to sort of work on my template is $list_id - > which displays as "testlist". (I was expecting to see > "testlist(a)example.com"). $listname should be replaced with the fqdn list name like "testlist(a)example.com" and $short_listname should be replaced with the list name without the @domain as in "testlist". The others should all work as documented. I don't know why they wouldn't. Can you give an example of a template that doesn't get these substituted. > The others just get displayed as a variable. Eg. $owner_email > > Have I missed a setting somewhere? The actual substitution is done by the Python `string` library module Template class, safe_substitute method. See the doc at https://docs.python.org/3/library/string.html#template-strings Note that because we use the safe_substitute method, invalid substitutions don't produce errors, they just aren't substituted. In particular if `$identifier` is followed immediately by a letter, digit or underscore, `identifier` must be wrapped in `{}` to separate it from the following characters, e.g., `${identifier}x`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: Message shows up individually but not in the thread

by Mark Sapiro

On 11/04/2017 01:19 AM, Marvin Gülker wrote: > Am 03. November 2017 um 12:35 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: >> Are you running all of Django's periodic tasks? > > They are running. This is the excerpt from /etc/crontab: ... > Obviously, mailman-suite is installed at /home/mailman/mailman-suite and > owned by user 'mailman', with the actual Django project in the > subdirectory 'mailman-suite_project', just as cloned from the Git > repository. The only difference from the official guide here is that I > took the liberty to place Mailman into two virtualenvs (a Python2 one > for the Django project, and a Python3 one for Mailman-Core*). > > There are no errors reported with this in /var/log/cron.log. And before > you ask, the task queue is running as well. The uWSGI config has this: > > # Setup the django_q related worker processes. > attach-daemon = ./manage.py qcluster > > And the qcluster process shows both up in the process list and is > happily logging away in the uWSGI log. There is a possibly related issues at <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones at <https://gitlab.com/mailman/hyperkitty/issues/131> and <https://gitlab.com/mailman/hyperkitty/issues/149>. I'm sorry I can't offer more help than that at this point. > * It'd be great if the mailman-suite was moved to Python 3 at some > point. That way one wouldn't need two separate virtualenvs. We're working on moving Postorius and HyperKitty to MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Re: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/15/20 11:13 AM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for your help! > > Yes, I meant "Today's Topic". The "Today's Topics" list is a plain text listing of the Subject: and sender of the messages in the digest. It is identical in both the plain text and MIME format digests. In what way is it cluttered with HTML. Please post an example. > I checked the link you sent, but could not see the solution to the issue. If the issue is HTML in the `Today's Topics:` list, then it is not <https://gitlab.com/mailman/mailman/-/issues/473>. If the HTML is in the messages themselves, then it is <https://gitlab.com/mailman/mailman/-/issues/473>, and that is currently not fixed and the workaround is to set Delivery mode to MIME digests. > You mentioned: > " They are in order of priority, list based, address based and global" > > Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? It's descending order, I.e. list overrides address overrides global. > I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: > acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings > are empty, even though I set them and saved. What Postorius version is this? Is this user a member with more than one role - e.g. more than one of member, nonmember, owner or moderator. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: No path configuration found: paths.master

by Abhilash Raj

On Thu, Oct 26, 2017, at 10:34 PM, Pierre Abbat wrote: > I installed postorius and hyperkitty with pip and ran into another > problem. I > ran "mailman info" and got "No path configuration found: paths.master". > > I have three files named mailman.cfg: > /etc/mailman.cfg > /usr/local/lib/python3.5/dist-packages/mailman/config/mailman.cfg > /var/etc/mailman.cfg > The one in /etc contains the following: > [mailman] > layout: master > The one in /var/etc is completely commented out. > > If I move the one in /etc/ out of the way and run "mailman info" again, I > get > this: > GNU Mailman 3.1.0 (Between The Wheels) > Python 3.5.2 (default, Sep 14 2017, 22:51:06) > [GCC 5.4.0 20160609] > config file: None > db url: sqlite:////etc/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > It said "config file: /var/etc/mailman.cfg" before. What changed? OK, this might be completely my mistake. I am very sorry about this. 'master' is usually only specified in schema and can't be used as valid value for 'layout'. I completely forgot this and updated the documentation to use 'master'. Please replace 'master' with 'local' and things should work. So, the config would look something like this: [mailman] layout: local I will go ahead and update the documentation right away. Hope this helps! > Pierre > -- > La sal en el mar es más que en la sangre. > Le sel dans la mer est plus que dans le sang. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 7 months

Re: What's the difference between (purpose of) reject and ignore

by Andy Smith

Hello, On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > AFAICS, it is not documented since, at Postorius → Settings → Message Acceptance → Default action to take when a (non-)member posts to the list, I only read: “Discard: this simply discards the message, with no notice sent to the post's author”. So no mention that this would set it to (silently) discard all future mails from them. Well that is because that isn't what that part does. As it says, that part is the "Default action to take when a member/non-member posts to the list". So that's where you set what you want to happen when ANY non-member posts. This is what will happen any time any non-member posts. By contrast, when you set an action on a particular held message, it is asking you want you want to do with posts from THAT INDIVIDUAL ADDRESS for the future. So hopefully you can see that these things are different. One is a whole-list property that applies to posts from classes of posters (members, non-members). The other is per-poster property as a reaction to as held message from them. > Just to be sure: for this feature, is it necessary to click on the > subject and to choose in the drop-down list “Discard (no > notification)”, or is it enough, on the .../held_messages page, to > select the messages and click on “Discard”? Doing it from the held messages page will be a one-time thing; it is only by clicking on the individual message that you can choose an action for future messages from that address. Cheers, Andy

3 years, 11 months

Re: Mailman not able to process "big" requests

by Jonas Felber

Thank you for your support, I got informed that we are now able to send out emails again. The problem was that the crashes we got while mass subscribing led to database corruptions. (From what I know, the problem was on our side, as we kubernetes did not properly restore some files after restarting so the database got corrupted (apparently we are running now a cleanup script on each restart)) There are still some problems, but I just wanted to send out a quick update. Thanks for your support, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch > On 24 Apr 2018, at 17:21, Darren Smith <silas.crutherton(a)gmail.com> wrote: > > Our installation at https://lists.rootsweb.ancestry.com has around 33,000 > lists and somewhere around 1.5 million members. We have lists with 5,000+ > members. > > Note that I haven't tried any mass subscriptions. When we upgraded from > mailman 2 to mailman 3, we used the old .pck files and ran the import on > each of the lists. It did take about 6 weeks to do the full import all > 33,000 lists. I'm not joking. > > As for sending messages - there isn't any problem sending that many > messages out, but then we are also not trying to subscribe list members at > the time. We are, though, in the process of importing the old archives from > our old mailman 2 system. This doesn't seem to affect the rest of the > system. > > We have seen some inefficiencies in the new system, such as the front page > of postorius - loading all of the information for 200 lists (if the user > set the "lists per page" to 200) was bringing down the system. We have our > own metadata system to be able to search for lists by state/region/surname > (ours is a genealogy mailing list system), so we had to replace the front > page with our own "find a list" functionality. > > The other main problem was the page where a user can see what lists they > subscribe to. That page was also a denial of service if the user had > several hundred lists they are subscribed to. And for a genealogy mailing > list system, this is common. > > We have actually ended up creating our own API layer (only accessible on > the local machine) and make certain calls to it for the most painful of the > issues. One of these days (when we get a moment to breathe) we are going to > post some of our changes to the project so that we can ditch our own API > and just use the internal REST API. > > To be fair, the inefficiencies are not necessarily with mailman or the rest > API itself - but with Postorius making hundreds of calls to load a single > page. Though if the API supported loading multiple lists at once instead of > having to load them serially, that might help as well. > > So while we have not seen any timeout issues on the call to mass subscribe > users, we HAVE found several other calls that are effectively a denial of > service and have gotten around them ourselves, with plans to contribute to > the project in the near future. > > -Darren > > >> On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 04/24/2018 12:36 AM, Abhilash Raj wrote: >>> On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> >>>> We also have a problem with sending out emails to "large" (>50) groups, >>>> as they seem to not getting sent out at all. Do you have any idea what >>>> the problem here could be? >>> >>> Which MTA are you using? What do you see in mailman's logs and MTA's >> logs? >>> >>> I haven't seen this kind of problem before with Mailman 3. This very >> list is hosted using Mailman 3 and I believe has more than 50 subscribers. >> >> >> Nor have I seen this issue. This list currently has 158 non-digest >> members. There are several @python.org Mailman 3 lists with over 100 >> non-digest members including the active yt-users(a)python.org list with >> 301 members, and I have gotten no reports of an issue like this. >> >> Also, there are over 600 lists at <https://lists.fedoraproject.org/>, >> and I don't think this is an issue there either. >> >> -- >> 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/ >> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 1 month

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Mon, Dec 26, 2022 at 5:07 PM Eggert Ehmke <eggert(a)eehmke.de> wrote: > Ok, > > I hope this is readable. I just copíed the content of some files into the > pastebin, don't know if it is possible to post tar.gz there. > https://pastebin.ubuntu.com/p/mmRJJwKDc3/ > > Just tell me if this works for you, and when something is missing. > Most of the settings are copied from some other sites and just adjusted > for my > needs. > Good luck! So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, right? Or it wasn't necessary? And what does your urls.py look like? My setup is PUBLIC for everyone so I will not hide the domain name :-) In my setup, MM3 is installed in /opt/mailman/mm/. and mod_wsgi is enabled in Apache. I am running uwsgi on a TCP socket, not unix socket. The whole of my *VHOST:* <CUT> WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman group=mailman python-path=/opt/mailman/mm:/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var WSGIRestrictSignal Off <VirtualHost *:443> ServerName mm3-lists.kictanet.or.ke SSLEngine on SSLCertificateFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/cert.pem" SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/privkey.pem" SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/chain.pem" CustomLog /var/log/mm3-lists-access.log combined ErrorLog /var/log/mm3-lists-error.log LogLevel info Alias /favicon.ico /opt/mailman/mm/static/hyperkitty/img/favicon.ico Alias /static "/opt/mailman/mm/static" <Directory "/opt/mailman/mm/static"> Require all granted </Directory> WSGIScriptAlias / /opt/mailman/mm/wsgi.py <Directory "/opt/mailman/mm/"> <Files wsgi.py> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> </CUT> *2. uwsgi.ini:* <CUT> [uwsgi] http-socket = 127.0.0.1:8000 pidfile = /opt/mailman/mm/var/uwsgi.pid chdir = /opt/mailman/mm/ virtualenv = /opt/mailman/mm/venv/ module=mailman_web.wsgi:application env =PYTHONPATH=/opt/mailman/mm/ env =DJANGO_SETTINGS_MODULE=settings master = true process = 2 threads = 2 attach-daemon = /opt/mailman/mm/venv/bin/mailman-web qcluster req-logger = file:/opt/mailman/mm/var/logs/uwsgi.log logger = qcluster file:/opt/mailman/mm/var/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons logger = cron file://opt/mailman/mm/var/logs/uwsgi-cron.log log-route = cron uwsgi-cron logger = file:/opt/mailman/mm/var/logs/uwsgi-error.log uid = mailman gid = mailman </CUT> *3. uwsgi - *Running supervised (supervisord): <CUT> [program:uwsgi] directory=/opt/mailman/mm/ environment=PYTHONPATH=/opt/mailman/mm/ command=/usr/bin/su -m mailman -c '/opt/mailman/mm/venv/bin/uwsgi --ini /opt/mailman/mm/uwsgi.ini' 2>&1 | logger -t uwsgi autostart=true autorestart=true user=mailman group=mailman stopasgroup=true killasgroup=true </CUT> *4. urls.py*: <CUT> from django.conf.urls import include from django.urls import re_path from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView from django_mailman3.views.profile import delete_account, user_profile urlpatterns = [ re_path(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), re_path(r'^user-profile/delete$', delete_account, name='mm_user_account_delete'), re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), re_path(r'^accounts/', include('allauth.urls')), re_path(r'^admin/', admin.site.urls), re_path(r'^mm/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ] </CUT> And that's pretty much what I am using on my FreeBSD server. PS: Possible to bottom-post instead of top-posting? :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 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 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years

Mailman-users search results for query "Postorius"