[Tickets #556] NEW: Sporadic login issue / qpopper I/O errors

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=556
-----------------------------------------------------------------------
 Ticket     | 556
 Created By | daniel at thinkhost.com
 Summary    | Sporadic login issue / qpopper I/O errors
 Queue      | IMP
 Version    | 3.2.5
 State      | Unconfirmed
 Priority   | 2. Medium
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


daniel at thinkhost.com (2004-09-09 11:39) wrote:

This problem is with IMP 3.2.5 and below, and has occurred with systems
running FreeBSD 4.9 and 4.10 systems that I can tell.

Basically, a user logs in to virtual mailbox, such as username at domain.com.
This is the user's username. Instead of redirecting to the user's mailbox,
there is some sort of I/O connection interruption. The browser sits at the
login screen. From /var/log/messages (with usernames and IPs filtered...):

Sep  9 14:21:50 alpha popper[26945]: [drac]: login by someuser from host
IP_ADDR (IP_ADDR)
Sep  9 14:21:51 alpha popper[26945]: someuser at IP_ADDR (IP_ADDR): -ERR POP
EOF or I/O Error
Sep  9 14:21:51 alpha popper[26945]: I/O error flushing output to client
someuser at IP_ADDR [IP_ADDR]: Operation not permitted (1)
Sep  9 14:21:53 alpha popper[26950]: [drac]: login by someuser from host
IP_ADDR (IP_ADDR)
Sep  9 14:21:53 alpha popper[26950]: someuser at IP_ADDR (IP_ADDR): -ERR POP
EOF or I/O Error
Sep  9 14:21:53 alpha popper[26950]: I/O error flushing output to client
someuser at IP_ADDR [IP_ADDR]: Operation not permitted (1

Although this would appear to be a problem with qpopper, it is not, as I am
able to login fine using a normal POP3 email client such as Outlook, Eudora,
Thunderbird, etc.

This problem only occurs with IMP to my knowledge and furthermore,
sporadically, only with some usernames. Permissions for working mailboxes
and those that give this error are identical. This is not a problem with the
system as far as I can tell.

One last thing to mention is that IMP is running on a webserver seperate
from the mailserver, so perhaps there is some timeout issue while connecting
to the mail server that IMP is not taking into account?

Since the problem occurs only with some users, I cannot reproduce the error
except with certain usernames at certain virtual hosts. For example, this
error will always happen with someuser at virtualhost@host, but not with
someotheruser at virtualhost@host.

Please let me know if you need clarification on any of this.