Nils writes:
> I've checked [for logs] in both locations. I even created a
> writeable syslog file in chroot to be sure. Neither had any
> information.
It's been a decade since I looked into the wrapper code, but I suspect
that the reason for the odd phrasing about "log will be written" is
due
Thank you very much for your help, Steve.
On 11/9/23 14:10, Stephen J. Turnbull wrote:
You're missing the bin directory and Python's files. Are they
correctly specified in the chroot?
The binaries are not mounted into chroot environment. Only selected
commands shall be available in jail. There
On 11/8/23 13:52, Nils wrote:
# sudo -u www-data /home/www/usr/lib/cgi-bin/mailman/listinfo
Content-type: text/html
Bug in Mailman version 2.1.26
Bug in Mailman version 2.1.26
We're sorry, we hit a bug!
Please inform the webmaster for this site of this
problem. Printing of traceback and other
Thank you both a lot, Odhiambo and Mark!
On 11/8/23 22:28, Mark Sapiro wrote:
As Odhiambo says, at this point you should be installing Mailman 3.
Further, issues with Debian/Ubuntu packages should be reported to Debian.
OK.
What do you get if you try to run, e.g.,
/usr/lib/cgi-bin/mailman/list
On 11/8/23 04:51, Nils wrote:
I can't get mailman version (1:2.1.26-1ubuntu0.6) to run on an ubuntu
18.04 installation with apache2 running in chroot. I've done the same
thing before, a long time ago and it worked perfectly back then.
As Odhiambo says, at this point you should be installing Ma
On Wed, Nov 8, 2023 at 8:08 PM Nils wrote:
> I can't get mailman version (1:2.1.26-1ubuntu0.6) to run on an ubuntu
> 18.04 installation with apache2 running in chroot. I've done the same
> thing before, a long time ago and it worked perfectly back then.
>
> chroot directory is /home/www
> (I admi
