> ---------------------------------------------------------------------- > aaron - 12-Jan-05 19:41 CET > ---------------------------------------------------------------------- > What the issue here? I don't believe that the envelope sender is kept > neither with lmtp nor with pipe/dbmail-smtp deliveries. Do you want to > start recording the envelope sender in the database?
This is a perfect example of why there ought to be a more generic per- message cache, rather than exclusively a header cache. While it would be pretty easy to make a fake header name for non-header data, it just seems cleaner to be able to tell easily which actually were message headers or not. Paul: you might keep that in mind as you begin work on the header caching. Need some way of marking headers vs. non-headers and a identifer for non-headers (could simply be a "header" flag, and name/value pair, along with references to message id, etc.). While on the subject, I'd like to be able to cache a couple flags per message for whether it's been forwarded, replied to, etc. With a good design for per-message data cache, would it make sense to move all the *_flag flags and maybe unique_id out of the message table down the road? They are basically the same thing, just specific to pop or imap. I don't think you'd get any space savings (in fact, would probably loose a little), but it might be a cleaner layout. -- Jesse Norell jesse @ kci.net
