[maildb-devel] Re: messages in/out of database

[<li...@av...>]

> For safety's sake (and probably only while we're developing/debugging),
> should we stash the entire (unmodified text) header in a table somewhere?

Sure, we can cram it somewhere.  :-)  I could just make a table called 
'msg_orig' that consists of the msg_id and a largetext field to hold the 
whole thing.  Ok? 

> Heck, let's err on the side of lots of options.  The idea here is that we
> can search and sort in a million different ways: 
> 
> - To
> - CC
> - BCC (for outgoing messages)
> - Subject
> - Date
> - In-Reply-To
> - Precedence
> - Reply-To
> - Sender
> - Message-ID (I think we have that already, right? Just mention it to be
>   complete...)
> - Return-Path
> - List-Id
> - X-Sender
> - X-Mailer
> - User-agent
> - Thread-topic
> - Thread-index
> - References
> - ...? 
> 

Errr...that's a lot.  Sure you don't want to keep just the "well-known" ones 
in msg_ids and shove the rest off into msg_hdrs?  Or do you want to get rid 
of msg_hdrs and put everything into msg_ids?  Actually I guess we'd need a 
msg_hdrs in any case to catch anything that we don't account for in msg_ids. 
Just wondering how far you want to go here. 

> Here's an issue, though: what happens if the value of any of these header
> lines is longer than the length of the "text" field?

Well, text is 64k, mediumtext is 16m, and largetext is 4g.  (I misspoke 
earlier when I said text was 16m.)  So...I'd make them mediumtext, I 
suspect, since I think 64k may be too small, but 16m has got to be overkill. 
I mean, I can't even get 1m message bodies sent half the time, much less 
anything with a header that big. 

 - Liza