Casper Langemeijer wrote: >> Also, duplication of cached data is *evil*. Consider using the >> dbmail_envelope >> table which contains all the senders, the recipients, date, subject and >> message-id information. Of course, it's in a IMAP compatible format, so >> you'll >> need to parse it. One tip: don't use regexp to do that. Write a tokenizer.
> That's exactly what I wanted! I've completely overlooked that one, I'm > very sorry. I thought about it a little more, and came to the conclusion that you probably don't want to use the _envelope table after all for two main reasons: - the content is quite difficult to parse. Like I said, you'll need to write a parser/tokenizer which is doable, but not trivial. - the content is semi-raw: though 8bit data in the fields will be utf8 encoded in the database, utf7 encoded subjects and addresses will be in their utf7 state. The headervalue table on the other hand is fully decoded and recoded as utf8: ready for presentation in a webapp. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
