I have exactly the same problem and couldn't solve it yet.
These are my packages:
ii imapproxy 1.2.4-5 IMAP
protocol proxy
ii php-net-imap 1.0.3-1 PHP
PEAR module implementing IMAP protocol
ii php5-imap 5.1.2-1 IMAP
module for php5
ii uw-imapd 2002edebian1-13 remote
mail folder access server
ii horde3 3.1.3-1 horde
web application framework
ii imp4 4.1.3-1 webmail
component for horde framework
for the moment I cannot change the imap server.
The syntoms are exactly the same of the original post: can login through
horde but when I go to imp I get, after a long wait an empty redirect.
In particular, when logging to horde these are the messages in the
system log:
Oct 6 22:34:15 localhost imapd[10477]: connect from 127.0.0.1 (127.0.0.1)
Oct 6 22:34:15 localhost imapd[10477]: imap service init from 127.0.0.1
Oct 6 22:34:15 localhost imapd[10477]: Authenticated user=****
host=localhost.localdomain [127.0.0.1]
Oct 6 22:34:15 localhost imapd[10477]: Logout user=****
host=localhost.localdomain [127.0.0.1]
and in the horde log:
Oct 06 22:34:15 HORDE [notice] [horde] Login success for ****
[151.37.72.107] to Horde [on line 90 of "/usr/share/horde3/login.php"]
then when I log to imp I get:
Oct 6 22:35:34 localhost imapd[10518]: connect from ***.***.***.***
(***.***.***.***)
Oct 6 22:35:34 localhost imapd[10518]: imaps SSL service init from
***.***.***.***
Oct 6 22:35:34 localhost imapd[10518]: Authenticated user=****
host=***.***.***.*** [***.***.***.***]
Oct 6 22:35:34 localhost imapd[10519]: connect from ***.***.***.***
(***.***.***.***)
Oct 6 22:35:34 localhost imapd[10519]: imaps SSL service init from
***.***.***.***
Oct 6 22:35:34 localhost imapd[10519]: Authenticated user=****
host=***.***.***.*** [***.***.***.***]
Oct 6 22:35:34 localhost imapd[10464]: Killed (lost mailbox lock)
user=**** host=***.***.***.*** [***.***.***.***]
I found the message Killed (lost mailbox lock) in the imap faq:
http://www.washington.edu/imap/IMAP-FAQs/index.html#7.19 which I quote here:
"This message only happens when either the traditional UNIX mailbox
format or MMDF format is in use. This format only allows one session to
have the mailbox open read/write at a time.
The servers assume that if a second session attempts to open the
mailbox, that means that the first session is probably owned by an
abandoned client. The common scenario here is a user who leaves his
client running at the office, and then tries to read his mail from home.
Through an internal mechanism called kiss of death, the second session
requests the first session to kill itself. When the first session
receives the "kiss of death", it issues the "Killed (lost mailbox lock)"
syslog message and terminates. The second session then seizes read/write
access, and becomes the new "first" session.
Certain poorly-designed clients routinely open multiple sessions to the
same mailbox; the users of those clients tend to get this message a lot.
Another cause of this message is a background "check for new mail" task
which does its work by opening a POP session to server every few
seconds. They do this because POP doesn't have a way to announce new mail.
The solution to both situations is to replace the client with a good
online IMAP client such as Pine. Life is too short to waste on POP
clients and poorly-designed IMAP clients."
so what could be the problem?
previous versions of imp4 used to work fine (the last working version
used to be imp4_4.0.2-2_all.deb)
any clue please?
thanks in advance
--
+-----------------------------------------------------+
| Lorenzo Bettini ICQ# lbetto, 16080134 |
| PhD in Computer Science, DSI, Univ. di Firenze |
| Florence - Italy (GNU/Linux User # 158233) |
| http://www.lorenzobettini.it |
| http://tronprog.blogspot.com BLOG |
| http://www.purplesucker.com Deep Purple Cover Band |
| http://www.gnu.org/software/src-highlite |
| http://www.gnu.org/software/gengetopt |
| http://www.lorenzobettini.it/software/gengen |
| http://www.lorenzobettini.it/software/doublecpp |
+-----------------------------------------------------+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
