MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR
I'm having this kind of trouble (see subject line) while opening my
inbox.
Using: pine 4.33 client on Debian GNU/Linux 2.2 (potato) ++
Linux my-box 2.2.17 #2 Wed Nov 8 16:30:49 CET 2000 i686
IMAP4rev1 v12.264 server ready
--- /etc/inetd.conf ---
imaps stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap \
-cert /etc/sslwrap/server.pem -port 143 -without_pid
---
I do receive "a lot" of messages and use pine's filtering features to
sort them out to different folders. This happens only when
establishing the connection to my imap server over ssl (port 993).
I do not experience this particular problem when either:
1. there are relatively few messages in my inbox (and ssl connect), or
2. I do have lots of new messages in my inbox, but I connect over an
ssh tunnel
Anyone else experiencing something similar?
Here are some of the relevant messages found in ~/.pine-debug1:
734:output_message(Opening "INBOX" )
744:d_q_status_message(Opening "INBOX" )
842:output_message(Moving 1 filtered message to "admin" )
905:d_q_status_message(Moving 1 filtered message to "admin" )
906:output_message(Moving 16 filtered messages to "admin" )
1210:d_q_status_message(Moving 16 filtered messages to "admin" )
1211:output_message(Moving 61 filtered messages to "spam" )
2114:d_q_status_message(Moving 61 filtered messages to "spam")
2115:d_q_status_message(Moving 61 filtered messages to "spam")
2116:d_q_status_message(Folder "INBOX" opened with 377 messages)
2117:output_message(MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR)
2119:d_q_status_message(MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS)
2120:d_q_status_message(Attempting to reopen closed folder "INBO)
2121:output_message(Opening "INBOX" )
2122:d_q_status_message(Opening "INBOX" )
9581:d_q_status_message(Opening "INBOX" DONE)
9582:d_q_status_message(Folder "INBOX" opened with 377 messages)
9583:output_message(MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR)
9595:d_q_status_message(MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS)
9596:output_message(UID sequence invalid)
9609:d_q_status_message(UID sequence invalid)
Yes, and I found some more:
alarm_signal()
IMAP mm_notify bye : {...:993/imap/ssl/novalidate-cert/user="..."}INBOX
(inboxstream) : IMAP connection broken (server response)
IMAP DEBUG 18:27:10 3/4: 000000b3 NO [CLOSED] IMAP connection broken
(server response)
IMAP 18:27:10 3/4 mm_log ERROR: [CLOSED] IMAP connection broken
(server response)
IMAP mm_notify bye : {...:993/imap/ssl/novalidate-cert/user="..."}INBOX
(inboxstream) : No-op dead stream
IMAP DEBUG 18:27:10 3/4: 000000b4 NO [CLOSED] No-op dead stream
IMAP 18:27:10 3/4 mm_log ERROR: [CLOSED] No-op dead stream
Impotent sslwrap/imap server(s)?
Anyone seen this before?
Any thoughts?
Recommendations?
Tips?
General good advice?
Therapy?
Medication?
Cheers :)
Cristian
PS. Incidentally, looking through the log, I see traces from an
earlier pine buffer overflow flopout caused by lengthy message
header entries, and which are now glued to the famous first
message in the mailbox.
Is there some way to wash that out?
>From MAILER-DAEMON Sun Mar 4 19:33:58 2001
Date: 04 Mar 2001 19:33:58 +0100
From: Mail System Internal Data <MAILER-DAEMON@...
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
Message-ID: <983730838@...
X-IMAP: 0968955312 0000066247 lesbo, homo, lesbian, anarchism,
nazi, communism, CIA, bomb, nuclear, Semtex, satan, traitor,
pedophile =?iso-8859-1?Q?kettutyt=F6
t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?=
Status: RO
Reply to: