Our web users connect via SSL so the password changes are tunneled in SSL any ways. Popper works fine. We just can't get poppassd to work. I get an error with it being busy. I am not sure I guessed at how to properly set up the xinetd.d file for poppassd. So my first two questions are:
1. Is special_auth required for Fedora?
2. Is the following accurate for a poppassd entry in xinetd.d?
service poppassd
{
port = 106
socket_type = stream
protocol = tcp
user = root
server = /usr/local/bin/poppassd
server_args = poppassd
wait = no
> instances = 4
disable = no
}
Tim
At 03:09 PM 11/18/2005, Daniel Senie wrote:
Because the POP Password service (poppassd) does not use encryption, I generally recommend against its use. Use a web-based password change mechanism instead.
As to your issues with special_auth, does popper itself interact successfully with user account authentication, or is it just poppassd that you have trouble with?
At 03:55 PM 11/18/2005, you wrote:
Qualcomm popper and poppassd experts,
I recently downloaded 4.08 of qpopper to install on a Fedora core 3 server. I compiled qpopper along with poppassd using the special_auth parameter. Correct me if I shouldn't include specail _auth. Popper appears to work just fine. However, get the following error from our webmail pop client from poppassd:
Failed to change Password {400 Server busy -- try again later.}I know that it sees the service, but the service is not responding appropriately.
I put these entries in /etc/xinetd.d/poppassd
service poppassd
{
port = 106
socket_type = stream
protocol = tcp
user = root
server = /usr/local/bin/poppassd
server_args = poppassd
wait = no
> instances = 4
disable = no
}
Is the above entry correct? Am I missing something? Can anyone suggest what I might be doing wrong to get the busy error above?
Tim Tyler
Network Engineer - Beloit College
[EMAIL PROTECTED]Tim Tyler
Network Engineer - Beloit College
[EMAIL PROTECTED]
