[imapfilter-devel] Disconnect, and then «BAD Please select a mailbox first»

[Lefteris Chatzimparmpas]

On 09/09/2010 10:59 PM, Joachim Tingvold wrote:
> Hi,
>
> I'm using IMAPfilter with my MobileMe-account. My config looks like
> this; <http://home.komsys.org/~jocke/imapfilter-config.lua>. I
> previously used «contain_», but as this took forever due to the amount
> of rules, I decided to use «match_», since combined with «enter_idle()»,
> this goes quite fast. The reason I chose to do this, was that I use push
> to my iPhone, and I don't want to have the «new email»-sound on all my
> list-emails, etc.

So far so good...

> So, over to my problem. IMAPfilter is running in a screen-session, and
> after a random timeframe, it looses the connection with MobileMe, and
> when it connects again, the following happens;
>
> S (4): * OK [CAPABILITY <snip>)
> C (4): 121E NOOP
> S (4): 121E OK Completed
> C (4): 121F CAPABILITY
> S (4): 121F OK CAPABILITY completed
> C (4): 1220 LOGIN "yep" *
> S (4): 1220 OK User logged in
> C (4): 1221 NAMESPACE
> S (4): 1221 OK Completed
> C (4): 1222 STATUS "INBOX" (MESSAGES RECENT UNSEEN)
> S (4): 1222 OK Completed
> 5945 messages, 0 recent, 4 unseen, in yep at mail.me.com/INBOX.
> C (4): 1223 UID SEARCH ALL NEW
> S (4): 1223 BAD Please select a mailbox first
> C (4): 1224 UID SEARCH ALL RECENT
> S (4): 1224 BAD Please select a mailbox first

Strange seems that mailbox is not selected while imapfilter things it
is... I would like to know what happens before this.  It would be nice
if you run imapfilter with the -d option and send me the relevant
sections from the ~/.imapfilter/debug.* file produced.  Make sure to
include the part a bit before what you've send me.

>
> It then goes into a loop, where it basically doesn't do shit (and no
> emails are moved/filtered);
>
> C (5): 11F4 IDLE
> S (5): 11F4 OK Completed
> C (5): 11F5 IDLE
> S (5): 11F5 OK Completed
> C (5): 11F6 IDLE
> S (5): 11F6 OK Completed
> C (5): 11F7 IDLE
> S (5): 11F7 OK Completed
> C (5): 11F8 IDLE

This is also strange... Some more details from the debug file might help
here, too...

> The error I've gotten when it looses the connection, has varied. The
> first message[1] is when I had the «options.timeout» set (to 120, FWIW).
> The second[2] and third[3] I've gotten about 50/50 after I removed the
> «options.timeout».

You might want to play with the keepalive option.  Try a value smaller
than the default 29...

> [1] imapfilter: timeout period expired while waiting to read data
> [2] imapfilter: reading data; EOF in violation of the protocol
> [3] imapfilter: reading data; the connection has been closed cleanly

As mentioned above, the context of those errors would probably help
understand why they happened...

> So, is this caused by something I'm doing wrong? Is this a known
> «issue»? Any help is appreciated.

Let's find out...