Martin Müller writes:
i found this message via google while searching for a solution but there is no rpm on debian/ubuntu systems and courier-authlib and courier-authlib-userdb are correctly installed. furthermore i did not have to build courier myself because ubuntu already has tha packages available.
If you installed packages that were built by someone else, and courier's courieresmtpd is not talking courier-authlib, you should raise this issue to the packager. This indicates a packaging miscompilation or a misconfiguration error of some sorts.
thing is... i can authenticate via pop and check for new mail. but the server soes not accept incoming mail -.-i'm quite frustrated^^
If it is not accepting incoming mail, and you see error messages that indicate that courier's esmtpd server cannot connect to courier-authlib's daemon, and is rejecting mail for this reason, then a broken package is the only explanation that I can think of. The courier package was not built against the same courier-authlib package that you have installed. It must be looking for a socket in a different directory. The directory where a socket gets created is defined at configuration time. There's a default value, but packages built for individual distributions commonly provide a distribution-specific value.
This looks like a packaging issue, try asking the packager for help looking into this.
pgpc4mgBaGtAK.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
