openwebmail broke with latest update
wfdudley at gmail.com
Tue Aug 27 03:43:52 UTC 2019
Again, thanks for your time on this.
My comments are interspersed below:
On Mon, Aug 26, 2019 at 1:53 AM MJ <mafsys1234 at gmail.com> wrote:
> Hi Bill,
> On 26/08/2019 12:30 am, William Dudley wrote:
> > Mark,
> > Thanks for your suggestions.
> > I left my debugging attempts out of my email to the list.
> > I checked the permissions, and they are as they should be: 4755 for
> > openwebmail.pl, owned by root:mail.
> Can you run the openwebmail.pl script in the directory?
If you mean run it from the command line, yes, I can, it poops out the
The bug occurs if I successfully login to openwebmail -- then I get the
> Look, curiosity took hold and I decided to install everything in a new VM,
> FreeBSD freebsd 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64
> (and that may be a problem, the version of bsd though I doubt it.)
I'm running 11.3, and I fear that the version of either Perl or openwebmail
is different between 11.3 and 12.0,
such that your test, while useful, may not have much bearing on my current
situation. At least, it suggests
that, when I upgrade to 12.x, openwebmail may once again work.
My pkg versions are:
apache24-2.4.41 (though I very much doubt apache has anything to do with
> Anyway, installed perl, apache and openwebmail. After a bit of torture
> with apache (I'm a lighttpd/nginx person I should've installed that - I
> just assumed you're running that, sorry) I got things working.
Yes, I use apache24, so that's the same.
> So, it's not the packages, it's a file. Perhaps check in
> /usr/local/www/cgi-bin/openwebmail if all the .files in there for the perl
> scripts have the correct permissions (these don't need the 's' sticky bit
> though, that's the domain of the C wrapper called openwebmail.pl). In my
> config they're all 755.
Yes, all the files are present; openwebmail isn't failing to run, it's
failing to do a change group.
For fun, I just uninstalled and re-installed openwebmail, to make sure all
files are present. There
was no change in the failure mode; still fails to change group.
More information about the freebsd-questions