Zenon Panoussis writes:
Classic problem, it gave me a lot of grief and it's not the first time it did. Posting the solution so that I know where to find it next time and it might help others in the meanwhile. IMAP_USELOCKS=1 IMAP_ENHANCEDIDLE=1 Apr 23 18:32:04 node01 imapd-ssl: Failed to connect to socket /tmp/fam--Apr 23 18:32:04 node01 imapd-ssl: Failed to create cache file: maildirwatch (user@domain)ps -A |grep gam |grep -v grep 21164 ? 00:00:00 gam_server The users are in LDAP, they all have different uidNumber:gidNumber and imapd spawns an instance under each user's uidNumber. Gamin however requires the LDAP users to be visible to the system, and mine were not.
Ok, so basically the IMAP server was getting started under a userid that's not known to the system.
Normally, when use LDAP, MySQL, or some other non-system module, with courier-authlib, they're set up to return the same userid for all accounts, which is also listed in passwd. That should work just fine, too.
pgpEx4g1GyIVd.pgp
Description: PGP signature
------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
