Hi Ilja,
Ilja Booij wrote:
Paul J Stevens wrote:
So apparently _ic_store and _ic_copy get fed invalid params so
check_state_and_args bails out without logging.
I've done some protocol scanning with ethereal.
dbmail is definitely sending back
BAD missing arguments to ...
so check_state_and_arg
Paul J Stevens wrote:
So apparently _ic_store and _ic_copy get fed invalid params so
check_state_and_args bails out without logging.
OK, I'll add some logging to those functions tomorrow, to see if I can
find any clues.
Ilja
Paul J Stevens wrote:
Ilja,
have you tried marking a
I did the same for uid copy. Same profile:
May 19 22:15:52 tsuki dbmail/imap4d[7472]: ParentSigHandler(): got
signal [14]
May 19 22:15:58 tsuki dbmail/imap4d[7479]: IMAPClientHandler(): line
read for PID 7479
May 19 22:15:58 tsuki dbmail/imap4d[7479]: COMMAND: [27 uid copy
321518,321520,321528
Ilja,
have you tried marking as read, restart tb and select the box.
After marking as read tb doesn't show them as unread anymore, but it
does so again after a close/select.
The logs also just don't smell right:
May 19 22:01:12 tsuki dbmail/imap4d[7472]: ParentSigHandler(): got
signal [14]
Ilja Booij wrote:
I've just sent myself 2500 messages. Moved them, read some of them after
that. Marked all as read. Moved all to trash, and expunged (compact
folder) them all.
all without a problem. It might be that some clients handle it
differently than other clients. I'm using Mozilla T
Hi Ilja,
> I've just sent myself 2500 messages. Moved them, read some of them after
> that. Marked all as read. Moved all to trash, and expunged (compact
> folder) them all.
>
> all without a problem. It might be that some clients handle it
> differently than other clients. I'm using Mozilla T
I've just sent myself 2500 messages. Moved them, read some of them after
that. Marked all as read. Moved all to trash, and expunged (compact
folder) them all.
all without a problem. It might be that some clients handle it
differently than other clients. I'm using Mozilla Thunderbird 0.6
Ilja
There are more bugs in the code wrt very large numbers of messages.
Try marking a box as read where there are 2000 unread messages.
It just don't work. Apparently imap4.c thinks a line has been read from the
client, where the client is still sending uids.
Ilja Booij wrote:
I have tried a fe
I have tried a few hundred, which worked fine.
I'll send myself some (2500) short emails to check if I have the same
problem.
Ilja
Thomas Mueller wrote:
While copying lot of messages to dbmail suddenly no new
connection was possible, imapd didn't respond any more.
Anyone any idea what I
> > While copying lot of messages to dbmail suddenly no new
> > connection was possible, imapd didn't respond any more.
Anyone any idea what I could do?
dbmail 2 is now my primary IMAP server (gets a copy of mails of the
former primary) and everything works very well - except when I copy a
large
> While copying lot of messages to dbmail suddenly no new
> connection was possible, imapd didn't respond any more.
I did some more tests: this seems to happen always after copying lot of
messages (last test where 2500). After all mails are copied the client
can still use the connection, other con
Hi,
I did several tests with current dbmail cvs with trace level 3 for
imapd. While copying lot of messages to dbmail suddenly no new
connection was possible, imapd didn't respond any more.
The last sign of life was:
May 16 14:55:37 geht-schon dbmail/imap4d[3825]:
dbpgsql.c,db_free_result: trying
12 matches
Mail list logo
