Try this:
make clean
./configure --enable-specialauth <-- This enables /etc/shadow usage.
make
Eric Luyten wrote:
> We upgraded Qualcomm popper version 3.1.2 to 4.0.2 last Friday
> and had to help a number of Outlook Express users (other admins
> have already posted the same on this mailing list).
>
> In a number of cases (all ?) the situation could be normalised by
> entering the user password in the appropriate OE configuration panel.
>
> We found that a combination of empty password field and a checked
> "remember password" box makes the client exhibit different behaviour
> with Qpopper 4 server versus version 3.
>
> Small illustration :
>
> % telnet XXXX pop3
> Trying [SNIP]...
> Connected to XXXX.
> Escape character is '^]'.
> +OK QPOP (version 3.1.2) at XXXX starting.
> user joeuser<CR>
> +OK Password required for joeuser.
> pass<CR> [several seconds wait]
> -ERR [AUTH] Password supplied for "joeuser" is incorrect.
> +OK Pop server at XXXX signing off.
> Connection closed by foreign host.
>
> % telnet YYYY pop3
> Trying [SNIP]...
> Connected to YYYY.
> Escape character is '^]'.
> +OK Qpopper (version 4.0.2) at YYYY starting.
> user joeuser<CR>
> +OK Password required for joeuser.
> pass<CR> [several MINUTES wait]
> -ERR POP timeout from YYYY
> +OK Pop server at YYYY signing off.
> Connection closed by foreign host.
>
> Other data :
> both servers are Solaris 7, shadow password files
> Qpopper was compiled in server mode, no APOP or Kerberos, no TLS
> (de)selecting "chunky-writes" makes no difference
>
> Hope this helps,
> Eric Luyten, Computing Centre VUB/ULB.
>
> P.S. Moving from Qpopper 3 to 4 makes for half the CPU utilisation
> and 60% less I/O on the mail spool partitions.
> Great job, Randall et al.
S/MIME Cryptographic Signature
