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

On Sun, 21 Dec 2025 12:25:45 +0000
Harry Duncan <[email protected]> wrote:

> 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).

Hi,

why 14.1? It's alredy EOL... current releases are 14.3 and 15.0. Recent
packages should be courier-1.5.1, courier-authlib-xxx-0.72.6, I see no
need to use sqwebmail package, it should be part of complete courier
package. Also looking at official ports repository, I see no 1.3.12
version for courier, it was 1.1.11 for some time and jumped directly to
1.5.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 have no experience with courier installed from packages, but building
all bits from ports as needed is not complicated, just somewhat lengthy.

> 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

Standard FreeBSD file hierarchy has no /var/sqwebmail directory, so
sqwebmail's socket should be located in /var/spool/courier directory, I
think you have something screwed a bit.

> 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

/usr/local/libexec/courier/webmail/webadmin (typo in your path, just
for precision) should be OK.

> 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

This should be OK as well.

> 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?

I do not have a directory with this name, but I do not use webadmin, so
I can't comment at the moment. I did check it in the past, but I do no
longer remember the details.

> 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.

I have server running with couriermlm running without issues, just a
note.

Regards,
Milan


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