Using dbmail-pop3d, I've been having problems where email shows up
out-of-sequence. I.e. I send an email with subject 1, wait for it to
enter dbamil via LMTP; send an email with subject 2, and wait again;
send an email with subject 3, and wait again; and then connect via
POP3. The order for the
On Mon, 2006-09-11 at 18:17 -0400, [EMAIL PROTECTED] wrote:
Using dbmail-pop3d, I've been having problems where email shows up
out-of-sequence. I.e. I send an email with subject 1, wait for it to
enter dbamil via LMTP; send an email with subject 2, and wait again;
send an email with subject
Am Montag, den 11.09.2006, 19:30 +0200 schrieb Paul J Stevens:
Lars Kneschke wrote:
Paul J Stevens [EMAIL PROTECTED] schrieb:
Now how about running your test with the latest svn codebase?
Just for the records.With the old codebase it took about 1 second to finnish
the tests in best case.
Am Montag, den 11.09.2006, 12:09 -0700 schrieb Aaron Stone:
On Mon, 2006-09-11 at 18:27 +0200, Lars Kneschke wrote:
Am Montag, den 11.09.2006, 08:45 +0200 schrieb Paul J Stevens:
Lars,
The only changes over the last week were in the FETCH code (not touched
in your examples), in the
On Tue, 2006-09-12 at 03:59 +0200, Lars Kneschke wrote:
g_strdup_printf does require the Solaris workaround in case one of its
arguments is null, so that's definitely something to look at.
Can you explain that a little bit further? Do you mean /usr/lib/[EMAIL
PROTECTED]
Yes exactly.
I
Am Montag, den 11.09.2006, 08:45 +0200 schrieb Paul J Stevens:
Lars,
The only changes over the last week were in the FETCH code (not touched
in your examples), in the sqlite layer and in the pop3 code. But I've
also been moving a lot of the trace calls in the imap code to Aaron's
newtrace
I don't think message ordering is provided in RFC?
I also don't think it is good policy to rely on message ordering.
Every message has it unique id, if you want to point out messages use
it.
That's most likely the order in which the database returns the
message id's .. eg. see what something like select message_idnr
from dbmail_messages where mailbox_idnr = returns, it's
probably the order you're seeing. You can turn logging up to level
5 to see the exact queries being run. As
I've added to the ORDER BY clause of the query in question. See if your
messages appear in a more consistent order now. I think it is a good
idea to return the messages in their id number order for consistency.
On Tue, 2006-09-12 at 08:39 -0600, Jesse Norell wrote:
That's most likely the order
