I found the problem... so for future trouble-shooting when somebody reports these symptoms:
Essentially the .courier-foo lookup was failing because the authentication process was failing with authldap. I had it in the list of modules for authdaemon, but had not set it up to work against any real LDAP server. The solution was to take authldap out of the module list (or, I suppose, to setup an LDAP server). -andy Bill Michell wrote: > Andrew Newton writes: > >> Bill Michell wrote: >> >>> >>> What's in the .courier-foo file? >> >> >> >> Good question. I tried just one line with the e-mail address to my >> PCS phone. So it is in the format [EMAIL PROTECTED] Suspecting >> it might be something wierd with either the format of the e-mail >> address or who knows, I changed it to another e-mail address for an >> account I have at Eskimo North (eskimo.com), but that didn't help either. >> I should note that I am using SMTP-AUTH with plain text login and >> STARTTLS to verify who can relay. The reason I bring this up is >> because one time I tried it I received the error message before I ever >> got prompted for my password. > > To test a little further, I suggest you make .courier-foo an *exact* > copy of .courier, including ownership, permissions and content. That'll > help track down where the problem lies. _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
