I'm trying to install Mailman3 on FreeBSD using
http://docs.mailman3.org/en/latest/prodsetup.html
The install runs but 'mailman info' returns errors.
Can anyone suggest where I should look to get this sorted out?
On Thu, 10 Aug 2017 20:56:56 +0100 John Poltorak <karotlopj@gmail.com> wrote:
I'm trying to install Mailman3 on FreeBSD using
http://docs.mailman3.org/en/latest/prodsetup.html
The install runs but 'mailman info' returns errors.
If you could show us what those errors are, it would help understand the problem.
thanks, Abhilash Raj
The instructions say
After this, create a configuration file at /etc/mailman.cfg for Mailman Core.
On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't see any indication as to what I should put in this file and if it was in /usr/local/etc/mailman.cfg then how would mailman find it?
I'm using a different system to install Mailman so it's difficult to paste the error msgs, but it seems to be related to being unable to find the module '_sqlite3'
On Thu, Aug 10, 2017 at 9:27 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, 10 Aug 2017 20:56:56 +0100 John Poltorak <karotlopj@gmail.com> wrote:
I'm trying to install Mailman3 on FreeBSD using
http://docs.mailman3.org/en/latest/prodsetup.html
The install runs but 'mailman info' returns errors.
If you could show us what those errors are, it would help understand the problem.
thanks, Abhilash Raj
On Aug 10, 2017, at 16:32, John Poltorak <karotlopj@gmail.com> wrote:
The instructions say
After this, create a configuration file at /etc/mailman.cfg for Mailman Core.
On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't see any indication as to what I should put in this file and if it was in /usr/local/etc/mailman.cfg then how would mailman find it?
It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro?
(Side note, you can always use -C /usr/local/etc/mailman.cfg or set the MAILMAN_CONFIG_FILE environment variable for alternative locations.)
I'm using a different system to install Mailman so it's difficult to paste the error msgs, but it seems to be related to being unable to find the module '_sqlite3'
That’s a Python problem. What does the following do for you?
% python3 Python 3.6.2 (default, Jul 27 2017, 18:13:18) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)] on darwin Type "help", "copyright", "credits" or "license" for more information.
import _sqlite3 _sqlite3 <module '_sqlite3' from '/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload/_sqlite3.cpython-36m-darwin.so’>
This is what you get from a Python 3.6 installed via homebrew on macOS.
Maybe you need to install another package to provide SQLite on FreeBSD?
-Barry
On 08/12/2017 04:51 PM, Barry Warsaw wrote:
On Aug 10, 2017, at 16:32, John Poltorak <karotlopj@gmail.com> wrote:
On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't see any indication as to what I should put in this file and if it was in /usr/local/etc/mailman.cfg then how would mailman find it?
It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro?
I was hoping Abhilash would chime in here, because I think John is using the docker image and there's probably a specific path for mailman.cfg.
As far as what goes in it, it could even be empty if you want to accept all the defaults, but you probably want at least
[mailman] site_owner: real_person@example.com
I expect if you do
find -name mailman.cfg
in your installation, you'll find at least examples.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 08/12/2017 04:51 PM, Barry Warsaw wrote:
On Aug 10, 2017, at 16:32, John Poltorak <karotlopj@gmail.com> wrote:
On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't see any indication as to what I should put in this file and if it was in /usr/local/etc/mailman.cfg then how would mailman find it?
It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro?
I was hoping Abhilash would chime in here, because I think John is using the docker image and there's probably a specific path for mailman.cfg.
As per his first message, I think John is using the prod setup from the documentaion1.
I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module.
The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable.
As far as what goes in it, it could even be empty if you want to accept all the defaults, but you probably want at least
[mailman] site_owner: real_person@example.com
I expect if you do
find -name mailman.cfg
in your installation, you'll find at least examples.
thanks, Abhilash
Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy
https://www.freebsd.org/cgi/man.cgi?hier(7)
Anything installed outside the base OS belongs in /usr/local
I guess that issue is something for the FreeBSD porters of Mailman3...
I'll use /etc/mailman.cfg for the time being but I don't know what should go in it. Can I see an example?
The other problem regarding sqlite was solved by
pkg install databases/py36-sqlite3
I'll get back to the install docs now. Thanks showing interest.
On Sun, Aug 13, 2017 at 2:25 AM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 08/12/2017 04:51 PM, Barry Warsaw wrote:
On Aug 10, 2017, at 16:32, John Poltorak <karotlopj@gmail.com> wrote:
On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't see any indication as to what I should put in this file and if it was in /usr/local/etc/mailman.cfg then how would mailman find it?
It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro?
I was hoping Abhilash would chime in here, because I think John is using the docker image and there's probably a specific path for mailman.cfg.
As per his first message, I think John is using the prod setup from the documentaion1.
I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module.
The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable.
As far as what goes in it, it could even be empty if you want to accept all the defaults, but you probably want at least
[mailman] site_owner: real_person@example.com
I expect if you do
find -name mailman.cfg
in your installation, you'll find at least examples.
thanks, Abhilash
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 13 August 2017 at 16:52, John Poltorak <karotlopj@gmail.com> wrote:
Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy
https://www.freebsd.org/cgi/man.cgi?hier(7)
Anything installed outside the base OS belongs in /usr/local
I guess that issue is something for the FreeBSD porters of Mailman3...
I'll use /etc/mailman.cfg for the time being but I don't know what should go in it. Can I see an example?
Try reading this document, especially backwards.
https://pythonhosted.org/mailman/src/mailman/docs/MTA.html
The other problem regarding sqlite was solved by
pkg install databases/py36-sqlite3
I'll get back to the install docs now. Thanks showing interest.
Kindly document your process during install so that you can share. Personally I have almost given up on MM3 on FreeBSD. You success might let me try again.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."
Thanks for the reference John,
On Aug 13, 2017, at 06:52, John Poltorak <karotlopj@gmail.com> wrote:
Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy
https://www.freebsd.org/cgi/man.cgi?hier(7)
Anything installed outside the base OS belongs in /usr/local
I looked over that page. Does this mean that even if you were to install Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want mailman.cfg in /usr/local/etc instead of /etc? That would differ from most Linux distributions where package manager installed packages would have their configuration files in /etc, and where “third party” packages would have them in /usr/local/etc.
I guess that issue is something for the FreeBSD porters of Mailman3…
I think so. I think for now I don’t want to support /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion if there are some more generic use cases. OTOH, the internal function that calculates the search paths could be refactored to make it easy for distributions to carry small deltas to add that as a search path (it really wouldn’t be that hard to do now, but it’s a little icky). Of course, you can’t add a configuration file to find a configuration file. :)
Cheers, -Barry
I'm making progress, albeit slowly. Any progress I make I will post on the FreeBSD forums...
https://forums.freebsd.org/threads/61050/
On Sun, Aug 13, 2017 at 7:14 PM, Barry Warsaw <barry@list.org> wrote:
Thanks for the reference John,
On Aug 13, 2017, at 06:52, John Poltorak <karotlopj@gmail.com> wrote:
Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy
https://www.freebsd.org/cgi/man.cgi?hier(7)
Anything installed outside the base OS belongs in /usr/local
I looked over that page. Does this mean that even if you were to install Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want mailman.cfg in /usr/local/etc instead of /etc? That would differ from most Linux distributions where package manager installed packages would have their configuration files in /etc, and where “third party” packages would have them in /usr/local/etc.
I guess that issue is something for the FreeBSD porters of Mailman3…
I think so. I think for now I don’t want to support /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion if there are some more generic use cases. OTOH, the internal function that calculates the search paths could be refactored to make it easy for distributions to carry small deltas to add that as a search path (it really wouldn’t be that hard to do now, but it’s a little icky). Of course, you can’t add a configuration file to find a configuration file. :)
Cheers, -Barry
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Third Party Config files on FreeBSD are to be found under /usr.local/etc. For instance apache, cups, rsync are to be found under /usr/local/etc/apache24, /usr/local/etc/cups, and /usr/local/etc/rsync respectively, but that is a problem for anyone who wants to port Mailman 3 to FreeBSD.
I guess one option would be to set mailman3-flags="--config-file=/usr/local/etc/mailman/mailman.cfg" in /etc/rc.conf or somesuch...
On Sun, Aug 13, 2017 at 7:23 PM, John Poltorak <karotlopj@gmail.com> wrote:
I'm making progress, albeit slowly. Any progress I make I will post on the FreeBSD forums...
https://forums.freebsd.org/threads/61050/
On Sun, Aug 13, 2017 at 7:14 PM, Barry Warsaw <barry@list.org> wrote:
Thanks for the reference John,
On Aug 13, 2017, at 06:52, John Poltorak <karotlopj@gmail.com> wrote:
Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy
https://www.freebsd.org/cgi/man.cgi?hier(7)
Anything installed outside the base OS belongs in /usr/local
I looked over that page. Does this mean that even if you were to install Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want mailman.cfg in /usr/local/etc instead of /etc? That would differ from most Linux distributions where package manager installed packages would have their configuration files in /etc, and where “third party” packages would have them in /usr/local/etc.
I guess that issue is something for the FreeBSD porters of Mailman3…
I think so. I think for now I don’t want to support /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion if there are some more generic use cases. OTOH, the internal function that calculates the search paths could be refactored to make it easy for distributions to carry small deltas to add that as a search path (it really wouldn’t be that hard to do now, but it’s a little icky). Of course, you can’t add a configuration file to find a configuration file. :)
Cheers, -Barry
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On Aug 13, 2017, at 11:08, Odhiambo Washington <odhiambo@gmail.com> wrote:
Try reading this document, especially backwards.
http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html
This one is much more up-to-date. pythonhosted.org was an old docs hosting service provided via the PyPI organization. It’s since been deprecated, and while the old links should no longer be public, I don’t think there’s a way to *physically* remove the old documentation.
readthedocs.io is so much better, too.
-Barry
On 14-Aug-17 13:26, Barry Warsaw wrote:
pythonhosted.org was an old docs hosting service provided via the PyPI organization. It’s since been deprecated, and while the old links should no longer be public, I don’t think there’s a way to *physically*
Can it be updated? E.g. replace the docs with really short ones: "Documentation for Mailman 3 has moved. Its new home is ..."
The search engines seem to pull up the old site - even though the site may be deprecated, that doesn't get all the wikis, blogs, e-mail archives, etc that reference it. Just about everyone who has tried to work with mm3 & written something here seems to start there... And once in that hole, keep digging :-(
Turning it into referrals would save people - and the folks who respond to them here - quite some pain.
(Not to mention those who are inhibited from posting by pride and/or language.)
FWIW
On Aug 14, 2017, at 10:46, tlhackque via Mailman-users <mailman-users@mailman3.org> wrote:
Can it be updated?
Unfortunately not by any knobs I can turn; none of that is exposed in the web ui. But I have asked the PyPI experts whether they can redirect or completely delete the old pages.
-Barry
participants (6)
-
Abhilash Raj -
Barry Warsaw -
John Poltorak -
Mark Sapiro -
Odhiambo Washington -
tlhackque