Re: FreeBSD webadmin "connect: No such file or directory" - socket/path issue

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============0195493667838300784==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-60851-1766321626-0001";
    micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 8bit

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_ripper.email-scan.com-60851-1766321626-0001
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Harry Duncan writes:

> =C2=AB HTML content follows
>
> =C2=BBHi
>
>
> I'm migrating an old working courier mail system from a custom-built (f=
rom =20
> sources) linux installation to FreeBSD 14.1 using the current packages =20
> (courier-1.3.12, courier-authlib-ldap-0.72.2, sqwebmail-6.2.12_1).
>
>
> I expected the deployement path to be easier and quicker than building =
from =20
> sources, but it hasn't, probably because I spent a lot of time doing di=
ff on =20
> config files etc.

One trick, for this sort of a thing, is to just copy the existing =20
configuration files into the to-be-installed, pre-created directory, and =20
then install the package.

Assuming that the package follows the instructions in INSTALL, sysconftoo=
l =20
will run during installation. It will remove individual obsoleted =20
configuration settings, preserve the unchanged configuration settings, an=
d =20
configuration settings that are not backward-compatible get reset to thei=
r =20
new defaults.


> I created issues and started over and had a cleaner run but =20
> could not get sqwebmail to run.
>
>
> I resolved sqwebmail running when I identified that it was expecting it=
s =20
> socket at /var/sqerbmail/sqerbmail.sock but the package created it at /=
var/=20
> spool/courier/sqwebmail.sock

This sounds like you were trying to ended up with a combination of both t=
he =20
standalone sqwebmail package and the webmail subpackage of Courier. This =20
looks like a packaging error.

> I moved to webadmin and am stuck.
>
>
> I have an SSL enabled apache which connects /cgi-bin/webadmin to /usr/l=
ocal/=20
> libexec/courier/werbmail/webadmin
>
>
> Accessing over the web consistently shows
> System unavailable
> (Connect: No such file or directory)
>
>
> I verified its setups bit is set correctly
> migrated over the /usr/local/etc/courier/webadmin/password with mode 40=
0 and =20
> owner courier
> verified added and removed sub directories exist
> used strings on the webadmin binary to find hardcoded paths and found:
>
>
> /usr/local/share/courier/courierwebadmin/<URL:http://webadmin.pl>webadm=
in.pl
> /var/spool/courier/webadmin
>
>
> There was nothing deployed to /var/spool/courier/webadmin by the packag=
e

That's where the socket lives.

> the question therefore is: What should /var/spool/courier/webadmin actu=
ally =20
> be?

Nothing. webadmin will create it, when it is started for real.

> On the old linux server there is no webadmin daemon running (ps / lsof =
show =20
> nothing)

There should be. I do not recall if in ancient times webadmin was just a =20
perl script, what's now webadmin.pl, and there was a separate suid wrappe=
r =20
for actually installing the updated configuration files.

The current instructions in INSTALL read:

OPTIONAL: Configure webadmin

   This is a web-based administration tool. webadmin is a web CGI
   application. It is necessary to have a local web server installed in o=
rder
   to use webadmin. Apache will do, but so will any other server with a
   complete CGI implementation (PHP is not required). Installing webadmin =
is
   a three step process:

   =C2=A01.=C2=A0Move /usr/lib/courier/libexec/courier/webmail/webadmin t=
o your web
       server's SSL cgi-bin directory.

   =C2=A02.=C2=A0Add the following command to your system startup script:

/var/www/cgi-bin/webadmin daemon &

Many packages, including my rpm packages, just install a symlink in the c=
gi-=20
bin directory instead of putting the binary there, but what you appear to =
be =20
missing is the step of starting webadmin, as per the above, as root.


--=_ripper.email-scan.com-60851-1766321626-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCaUft2gAKCRCKYPgoojZS
4jGfAQDnvCM3diENX8WbQwMjb4LQY0WWXQuQX/XFC162rF2qBgEAsOfFYh/CQ+7t
D+wc5u3PoaUqs760tR8WVoL6CfD61Qo=
=JW6J
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-60851-1766321626-0001--


--===============0195493667838300784==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0195493667838300784==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

--===============0195493667838300784==--