From: Paul J Stevens dbmail-dev@dbmail.org
snip
What I like about the yukatan approach is that it tries to make searches on
very common headers as cheap and
fast as possible. It does this by going one step beyond separate header
storage: preparse certain headers for
common attributes:
Jesse Norell wrote:
Isn't this exactly what the header/message cache will do, as well? With
a nice, generic setup, I had hoped to do exactly that - cache the In-Reply-To
and References headers to enable quick/easy message threading in weDBmail.
I guess I was just wondering if this whole thread
The following bug has been SUBMITTED.
==
http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=145
==
Reported By:bjohnson
Assigned
Entered into the tracker as #145. I also included enough logging to
hopefully show that it is happening. Please excuse the semi-sanitized
files (for privacy reasons).
Bernard
Paul J Stevens wrote:
Bernard,
Could you please report this issue on the bugtracker on www.dbmail.org.
Please
Aaron,
I'm working toward a unified implementation for both functions. But what I don't
understand is the reason for splitting them up in the first place. Ok, so
_network does more checking on the state of the instream, but other than
that...?? Ownership of the stream I'm guessing?
--
On Tue, 04 Jan 2005 16:38:14 +0100, Paul J Stevens [EMAIL PROTECTED] wrote:
Aaron,
I'm working toward a unified implementation for both functions. But what I
don't
understand is the reason for splitting them up in the first place. Ok, so
_network does more checking on the state of the
Ilja Booij [EMAIL PROTECTED] said:
Paul J Stevens [EMAIL PROTECTED] wrote:
I'm working toward a unified implementation for both functions. But what
I don't understand is the reason for splitting them up in the first place.
Ok, so _network does more checking on the state of the instream, but
Mmm. Should stdin injection support more than one message at a time? Can I rely
on eof?
From reading the relevant parts of gmime I've come to suspect gmime will read until eof unless the parser is
satisfied a complete message has been read (due to mime-part parsing, i.e boundary detection).
