[MM3-users]Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4
Hello World! Very nice to meet you all this afternoon!
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.
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.
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks Mark for your time. I will follow your recommendation and try mailman bundler again, with care so that new conflicts won't occur as happened yesterday.
Mailman bundler docs, in the first paragraph, refer to combined installation of GNU Mailman, Postotius, and Hyperkitty. Does that mean that mailman.client will be installed later separately?
My CentOs 7 distribution does not offer python3.4.pip. https://pypi.python.org/pypi/pip offers pip 8.1.2 in two versions:
Python Wheel pip-8.1.2-py2.py3-none-any.whl (md5, pgp) Source pip-8.1.2.tar.gz (md5, pgp)
Which one should I choose?
I also notice that postfix is required. yum offers the following options:
pcp-pmda-postfix.x86_64 : Performance Co-Pilot (PCP) metrics for the Postfix (MTA) postfix.x86_64 : Postfix Mail Transport Agent postfix-perl-scripts.x86_64 : Postfix utilities written in perl postfix-sysvinit.noarch : SysV initscript for postfix spamass-milter-postfix.noarch : Postfix support for spamass-milter postgrey.noarch : Postfix Greylisting Policy Server pypolicyd-spf.noarch : SPF Policy Server for Postfix (Python implementation) sqlgrey.noarch : Postfix grey-listing policy service
Which of these options are useful? Which ones are unnecessary?
Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar.
Best regards,
Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)
Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)
2016-05-28 14:06 GMT-04:00 Mark Sapiro <mark@msapiro.net>:
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Thanks Mark for your time. I will follow your recommendation and try mailman bundler again, with care so that new conflicts won't occur as happened yesterday.
Mailman bundler docs, in the first paragraph, refer to combined installation of GNU Mailman, Postotius, and Hyperkitty. Does that mean that mailman.client will be installed later separately? It will be installed in the python2 virtualenv
My CentOs 7 distribution does not offer python3.4.pip. https://pypi.python.org/pypi/pip offers pip 8.1.2 in two versions:
Python Wheel pip-8.1.2-py2.py3-none-any.whl (md5, pgp) Source pip-8.1.2.tar.gz (md5, pgp)
Which one should I choose? I don't use centos, but google is your friend: http://www.liquidweb.com/kb/how-to-install-pip-on-centos-7/
I also notice that postfix is required. Setting up postfix (MTA) is a completely different topic which needs careful configuring and tuning. There are tons of tutorials out there
On 05/28/2016 09:03 PM, Rubén Rivero Capriles wrote: that help you with setting it up. Since there are so many options, no one here can tell you how to set it up. Mailman only requires the "postmap" command to generate files that tell postfix what emails it should accept and where to route them. You will of course need a complete postfix installation in order to actually send and receive emails.
Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar. Not sure what your question regarding avatars is. If you mean the gravatars shown on hyperkitty, then you'll need to upload a picture to gravatar.com
Very nice to meet you too Simon.
Yesterday I downloaded and installed pip and other tools required for Mailman bundle. However I must be very careful because the docs make a distinction between pip for python 2.7 needed during installation, and pip 3.4 needed for an already installed Mailman Core. The link you provided shows an example of a yum installation for pip 1.3.1. The mailman bundler documentation proposes a pip 8.1.2 installation which I assume is specifically suitable to pythos 3.4 and the Mailman Core.
My precise question is: should I yum install pip for python 2.7 now? Will I later install pip from sources for python 3.4 for the core, once mailman bundler is completed?
Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)
I also notice that postfix is required.
Setting up postfix (MTA) is a completely different topic which needs careful configuring and tuning. There are tons of tutorials out there that help you with setting it up. Since there are so many options, no one here can tell you how to set it up. Mailman only requires the "postmap" command to generate files that tell postfix what emails it should accept and where to route them. You will of course need a complete postfix installation in order to actually send and receive emails.
Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar. Not sure what your question regarding avatars is. If you mean the gravatars shown on hyperkitty, then you'll need to upload a picture to gravatar.com
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 05/28/2016 09:47 PM, Rubén Rivero Capriles wrote:
My precise question is: should I yum install pip for python 2.7 now? Will I later install pip from sources for python 3.4 for the core, once mailman bundler is completed? If you install it using the EPEL repos, you should end up with pip 7.1 You should always try to get it from an official repo first. bundler needs python3.4 and python2.7. It also needs pip and virtualenv installed for both versions. You have to make sure they are installed before you start with the bundler installation instructions.
I don't think there should be any issues with outdated pip versions. The one thing I know of that changed, is how dependencies are handled, so you might need to install some dependencies by hand.
On 05/28/2016 12:47 PM, Rubén Rivero Capriles wrote:
My precise question is: should I yum install pip for python 2.7 now? Will I later install pip from sources for python 3.4 for the core, once mailman bundler is completed?
There are both Python 2 and Python 3 versions of pip. You need both. See <http://mailman-bundler.readthedocs.io/en/latest/>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 28, 2016, at 11:06 AM, Mark Sapiro wrote:
There is also mailman.client which provides Python bindings for the REST API. This is Python 2.
Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y for some versions of x and y.
Cheers, -Barry
On 05/28/2016 01:44 PM, Barry Warsaw wrote:
Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y for some versions of x and y.
You are probably correct. It installs just fine with
python3 setup.py install
but both Hyperkitty and Postorius import it and they are Python 2, so I think with those pieces it needs to be Python 2.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y for some versions of x and y.
Cheers, -Barry
Hi Barry, it doesn't seem the case. Yesterday I dealt simultaneously with random downloads of either version for various packages, which incurred into unrecoverable conflicts with firewalld. For that reason I decided to reinstall OS this morning. I will focus first on running postfix, Then will carefully follow instructions for each version separately. Only then it will be advisable to run mailman bundler. I learned it yesterday the hard way! Thanks by the way for including me in this list and I wish all of you the best for completion of your projects.
Sincerely, Rubén
(please note that I earlier replied this by email, as I notice that it doesn't show up on the list website I am reposting. Hopefully it won't be repeated. I've been looking through archive posts and some are double. Would be interesting to check if my reply from half an hour ago will eventually get posted. If it gets, my apologies!)
On 05/28/2016 02:19 PM, Rubén Rivero Capriles wrote:
(please note that I earlier replied this by email, as I notice that it doesn't show up on the list website I am reposting. Hopefully it won't be repeated. I've been looking through archive posts and some are double. Would be interesting to check if my reply from half an hour ago will eventually get posted. If it gets, my apologies!)
Your initial reply was sent to the list members. It should have been archived, but it wasn't. That is my fault as I was experimenting with a Python 3 version of mailman.client which didn't work and then for a short time I had stopped the web services but not the core, and your post arrived during that window and was unable to be archived.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear mailman team,
Before installation of postfix, I would like to remove a cron scheduled mail from awstats that arrives every 30 minutes to /var/log belonging to a misconfigured, deleted awstats configuration, reminding me that such file does not exist. Still looking for the most suitable way to learn about cron. Awstats documentation informs there is statistics support for mail activities besides traditional website visits monitoring. Does mailman work along well with awstats?
Dear mailman team,
Before installation of postfix, I would like to remove a cron scheduled mail from awstats that arrives every 30 minutes to /var/log belonging to a misconfigured, deleted awstats configuration, reminding me that such file does not exist. Still looking for the most suitable way to learn about cron. Your OS docs should have information about what program is responsible for handling cron entries.
man crontabshould have information on how to read and write the cron config Awstats documentation informs there is statistics support for mail activities besides traditional website visits monitoring. Does mailman work along well with awstats? I have no idea what awstats does, but it probably only reads postfix' logs. So it actually doesn't care about mailman. There might be a way for it to parse mailman logs directly. If there is a way it's most
On 05/30/2016 07:19 PM, Rubén Rivero Capriles wrote: probably for mailman 2 and might be incompatible with mailman 3
On 5/30/2016 3:13 PM, Simon Hanna wrote:
Dear mailman team,
Before installation of postfix, I would like to remove a cron scheduled mail from awstats that arrives every 30 minutes to /var/log belonging to a misconfigured, deleted awstats configuration, reminding me that such file does not exist. Still looking for the most suitable way to learn about cron. Your OS docs should have information about what program is responsible for handling cron entries.
man crontabshould have information on how to read and write the cron config Awstats documentation informs there is statistics support for mail activities besides traditional website visits monitoring. Does mailman work along well with awstats? I have no idea what awstats does, but it probably only reads postfix' logs. So it actually doesn't care about mailman. There might be a way for it to parse mailman logs directly. If there is a way it's mostOn 05/30/2016 07:19 PM, Rubén Rivero Capriles wrote: probably for mailman 2 and might be incompatible with mailman 3
awstats (http://www.awstats.org/) is a logfile analyser used mostly for analysing and generating stats for websites. It can do email and other logs as well. Depending on what OS you are using determines where to find the cron files,which may or may not run as root ;)
On 5/30/16 10:19 AM, Rubén Rivero Capriles wrote:
Does mailman work along well with awstats?
Probably not.
mmdsr (Mailman Daily Status Report) is a fairly comprehensive log reporting tool for Mailman 2.1, but it hasn't yet been ported for Mailman 3.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi! sorry for updating one last piece of info provided by Thomas Woerner of firewalld. He seems interested in our issue of python 2 / python 3:
Thomas Woerner <notifications@github.com> 4:12 (hace 3 horas) para t-woerner/fire., mí, Author
Do you want to use python2 or python3? In the firewalld repo there is a firewalld.spec file. With this it is simply to generate packages for Fedora and also RHEL >= 7. For RHEL-7 it is still using python2, for Fedora >= 23 python3. TO build a package with it you can simple do the following in the root directory of the firewalld source tree:
./autogen.sh make test-rpm
Or you can use
rpmbuild -ta firewalld-0.4.2.tar.gz
with a release from https://fedorahosted.org/released/firewalld/ or https://github.com/t-woerner/firewalld/releases
I am still stuck with awstats. Have been able to watch them through lynx linux browser, but stats are not being generated. I enrolled in a local linux academy where I will take an apache course and maybe they''ll be of help. However I don't like software that does not provide support themselves, especially if good folks such as mailman or firewalld team are around. Is there any alternative statistics generation package for apache that you could recommend and I would be able to use without so many installation issues
Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)
participants (5)
-
Barry Warsaw -
Mark Sapiro -
Richard Shetron -
Rubén Rivero Capriles -
Simon Hanna