[Bug 250362] mail/mailman3: zope.interface>=5.0 is required

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jan 18 11:56:33 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250362

Marko Cupać <marko.cupac at mimar.rs> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marko.cupac at mimar.rs

--- Comment #35 from Marko Cupać <marko.cupac at mimar.rs> ---
Hi everyone,

I have just made my first mailman3 (suite) installation on FreeBSD work. Took
me some time and nerves :) but it works.

As for mailman itself, it almost works just by installing mail/mailman3. As Dan
said on his blog, it is throwing some errors on `service mailman start`, which
are resolved by installing additional packages which are undeclared
dependencies. All the ports/packages are already in official ports tree. Latest
devel/py-zope.interface 5.2.0 is trivial to compile from ports (poudriere),
just needs latest revision in Makefile + make makesum.

As for web suite (postorius + hyperkitty), I solved it through pip in
virtualenv. It also needed textproc/sassc globally installed with pkg, and also
hyperkitty (or was it mailman-hyperkitty?) installed globally with pip as there
is no port as of yet.

Current verdict: it works and it is possible to set up. But it is quite
complicated from admin's point of view, as it needs compiling custom ports,
mixing pip and pkg for installation of base python packages, and additional
virtualenv for web suite. Also it takes at least 3 different config files.

>From my (admin's) point of view, it would be best if mailman3 was ported to
FreeBSD as three (meta) ports, similar to:
mailman (core)
mailman (web) 
mailman (full) - core + web


All should be installable with pkg, and all should be started from rc.conf.

I'd be glad to help if someone told me how.

Regards,

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list