On Sat, 1 Jan 2005 01:21:58 +0059, Claudio Jeker <[EMAIL PROTECTED]> wrote: > On Fri, Dec 31, 2004 at 12:14:20AM -0500, Daniel Corbe wrote: > > On Thu, 30 Dec 2004 23:58:12 -0500, Daniel Corbe > > <[EMAIL PROTECTED]> wrote: > > > On Thu, 30 Dec 2004 23:51:01 -0500, Daniel Corbe > > > <[EMAIL PROTECTED]> wrote: > > > > On Thu, 30 Dec 2004 18:50:59 -0800, Chris Wilkes > > > > <[EMAIL PROTECTED]> wrote: > > > > > On Thu, Dec 30, 2004 at 04:07:21PM -0500, Daniel Corbe wrote: > > > > > > > > > > > > When I go to pop in I get this: > > > > > > > > > > > > user [EMAIL PROTECTED] > > > > > > +OK > > > > > > PASS xxxxxxx > > > > > > -ERR unable to write pipe > > > > > > > > > > > > What does that mean? > > > > > > > > > > What do the logs say? Are you able to do an *authenicated* ldap > > > > > search > > > > > with that username and password? > > > > > > > > > > And please don't top post, insteading posting your answer after the > > > > > question. Don't mean to be rude but it made it near impossible to > > > > > follow a thread that goes like this: > > > > > Maple! > > > > > No what street > > > > > Boston > > > > > Where do you live? > > > > > > > > > > Chris > > > > > > > > > > > > > The logs seem to indicate a successful POP session: although I don't > > > > know what "status 256" means, I assume that's an exit code? if so > > > > what is 256? > > > > > > > > @4000000041d478490bbed7f4 tcpserver: status: 0/40 > > > > @4000000041d47aa10869483c tcpserver: status: 1/40 > > > > @4000000041d47aa1086953f4 tcpserver: pid 14857 from 66.165.175.229 > > > > @4000000041d47aa10879ceb4 tcpserver: ok 14857 > > > > monitor1.mia.network.eglobalphone.com:66.165.175.5:110 > > > > :66.165.175.229::60606 > > > > @4000000041d47aa10aaea074 tcpserver: end 14857 status 256 > > > > @4000000041d47aa10aaea844 tcpserver: status: 0/40 > > > > @4000000041d486971f341b14 tcpserver: status: 0/40 > > > > > > > > I can authenticate against LDAP with that user (I do it all the time) > > > > and I'm pretty sure it works like its supposed to. I'm not as > > > > familiar with the command line utils as I could be so I'm not sure if > > > > I'm even doing this right, but when I do an ldapsearch authed against > > > > my credentials I get this: > > > > > > > > [EMAIL PROTECTED] root]# ldapsearch -b "dc=voipincorporated,dc=com" -x > > > > -W -D > > > > "uid=dcorbe,ou=People,dc=voipincorporated,dc=com" '(uid=dcorbe)' > > > > Enter LDAP Password: > > > > version: 2 > > > > > > > > # > > > > # filter: (objectClass=*) > > > > # requesting: ALL > > > > # > > > > > > > > # search result > > > > search: 2 > > > > result: 0 Success > > > > > > > > # numResponses: 1 > > > > > > > > I run the same ldapsearch with the qmail user and get the same result. > > > > I know qmail works though because smtpd delivery works. > > > > > > > > When I run the query as manager it works as expected. > > > > > > > > Not sure. > > > > > > > > Now, looking through the archives, it would seem to suggest that some > > > > people have pointed out that auth_pop may or may not need more > > > > permissions than it gets by default (or that I'm giving it) in order > > > > to succeed; however, no real answer has ever been given. Is this > > > > true? Not true? does auth_pop need to be run as root? > > > > > > > > Thanks, > > > > Daniel > > > > > > > > P.S. sorry about the top posts. > > > > > > > > > > > > > This almost seems like extremely relevant information > > > > > > http://qmail-ldap.suares.com/pipermail/qmail-ldap-archive/2000-October/002634.html > > > > > > > okay, I just confirmed that it may be true (to a point) > > > > After I changed the -u and -g flags to tcpserver from vmail's UID and > > vmail's GID, I now no longer get the "cannot write to pipe" error; > > however, authentication is failing: > > > > +OK <[EMAIL PROTECTED]> > > USER [EMAIL PROTECTED] > > +OK > > PASS xxxxxxxx > > -ERR authorization failed > > > > Similarly, the log files don't indicate why. > > > > -Daniel > > Hmm. Your ldapsearch is looking for (uid=dcorbe) whereas in the pop3 > session you are using [EMAIL PROTECTED] which turns into > ([EMAIL PROTECTED]). So these are two different searches. > > -- > :wq Claudio >
+OK <[EMAIL PROTECTED]> USER dcorbe +OK PASS xxxxxxxxx -ERR authorization failed Same thing -Daniel
