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

Harry Duncan <[email protected]> Sun, 21 Dec 2025 12:25:45 +0000
Newsgroups gmane.mail.imap.courier.general
Message-ID <CAHAPYVAHb9g-cGh9_jDmsWZVsF5ac0MR2aEW+Hj8M5Bg6SiyRA@mail.gmail.com>
--===============6628089128124519497==
Content-Type: multipart/alternative; boundary="00000000000097e11606467569c4"

--00000000000097e11606467569c4
Content-Type: text/plain; charset="UTF-8"

Hi

I'm migrating an old working courier mail system from a custom-built (from
sources) linux installation to FreeBSD 14.1 using the current packages
(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
sources, but it hasn't, probably because I spent a lot of time doing diff
on config files etc. I created issues and started over and had a cleaner
run but could not get sqwebmail to run.

I resolved sqwebmail running when I identified that it was expecting its
socket at /var/sqerbmail/sqerbmail.sock but the package created it at
/var/spool/courier/sqwebmail.sock

I resolved this with a symlink and sqwebmail runs perfectly now.

I moved to webadmin and am stuck.

I have an SSL enabled apache which connects /cgi-bin/webadmin to
/usr/local/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 400
and 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/webadmin.pl
/var/spool/courier/webadmin

There was nothing deployed to /var/spool/courier/webadmin by the package

verified /usr/local/share/courier/courierwebadmin/webadmin.pl exists along
with other support files (admin-main.pl dumping.pl etc)
created /var/spool/courier/webadmin as a directory (mode 700 with owner
courier, but this changed the error to "socket operation on non-socket
Removed the directory - error revered to no such file or directory

the question therefore is: What should /var/spool/courier/webadmin actually
be?

On the old linux server there is no webadmin daemon running (ps / lsof show
nothing)
The webadmin binary is setups root so it shouldn't need a separate daemon
there is no socket file for webadmin on the working linux system
Is this path supposed to be a working director, a socket created on demand
or something else?

If you need more system specifics just ask.

Any guidance greatly appreciated.

Thanks

Harry.

ps. Couriermlm is broken too in the package, but I'm not interested in that
as I don't use it.

--00000000000097e11606467569c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi<div><br></div><div>I&#39;m migrating an old working cou=
rier mail system from a custom-built (from sources) linux installation to F=
reeBSD 14.1 using the current packages (courier-1.3.12, courier-authlib-lda=
p-0.72.2, sqwebmail-6.2.12_1).</div><div><br></div><div>I expected the depl=
oyement path to be easier and quicker than building from sources, but it ha=
sn&#39;t, probably because I spent a lot of time doing diff on config files=
 etc. I created issues and started over and had a cleaner run but could not=
 get sqwebmail to run.</div><div><br></div><div>I resolved sqwebmail runnin=
g when I identified that it was expecting its socket at /var/sqerbmail/sqer=
bmail.sock but the package created it at /var/spool/courier/sqwebmail.sock<=
/div><div><br></div><div>I resolved this with a symlink and sqwebmail runs =
perfectly now.</div><div><br></div><div>I moved to webadmin and am stuck.</=
div><div><br></div><div>I have an SSL enabled apache which connects /cgi-bi=
n/webadmin to /usr/local/libexec/courier/werbmail/webadmin</div><div><br></=
div><div>Accessing over the web consistently shows</div><div>System unavail=
able</div><div>(Connect: No such file or directory)</div><div><br></div><di=
v>I verified its setups bit is set correctly</div><div>migrated over the /u=
sr/local/etc/courier/webadmin/password with mode 400 and owner courier</div=
><div>verified added and removed sub directories exist</div><div>used strin=
gs on the webadmin binary to find hardcoded paths and found:</div><div><br>=
</div><div>/usr/local/share/courier/courierwebadmin/<a href=3D"http://webad=
min.pl">webadmin.pl</a></div><div>/var/spool/courier/webadmin</div><div><br=
></div><div>There was nothing deployed to /var/spool/courier/webadmin by th=
e package</div><div><br></div><div>verified /usr/local/share/courier/courie=
rwebadmin/<a href=3D"http://webadmin.pl">webadmin.pl</a> exists along with =
other support files (<a href=3D"http://admin-main.pl">admin-main.pl</a> <a =
href=3D"http://dumping.pl">dumping.pl</a> etc)</div><div>created /var/spool=
/courier/webadmin as a directory (mode 700 with owner courier, but this cha=
nged the error to &quot;socket operation on non-socket</div><div>Removed th=
e directory - error revered to no such file or directory</div><div><br></di=
v><div>the question therefore is: What should /var/spool/courier/webadmin a=
ctually be?</div><div><br></div><div>On the old linux server there is no we=
badmin daemon running (ps / lsof show nothing)</div><div>The webadmin binar=
y is setups root so it shouldn&#39;t need a separate daemon</div><div>there=
 is no socket file for webadmin on the working linux system</div><div>Is th=
is path supposed to be a working director, a socket created on demand or so=
mething else?</div><div><br></div><div>If you need more system specifics ju=
st ask.</div><div><br></div><div>Any guidance greatly appreciated.</div><di=
v><br></div><div>Thanks=C2=A0</div><div><br></div><div>Harry.</div><div><br=
></div><div>ps. Couriermlm is broken too in the package, but I&#39;m not in=
terested in that as I don&#39;t use it.</div></div>

--00000000000097e11606467569c4--


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


--===============6628089128124519497==
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

--===============6628089128124519497==--