Okay, so the problem that you are having is getting the whole e-mail message into the database? And you are storing the entire e-mail message into 'thetips' table? I'm assuming that after you have messages that contain tips in 'thetips' table, they will moved into the 'content' table later, correct? Dean Seth Bienek writes: > I have written a process to do this.. The only problem thus far is > reading in the 50+ MB mail archive file and processing the whole > thing without any exceptions. > > I guess I should explain that. I wrote a custom tag to parse the > tips, and another to parse the mail archive into a the database. > The idea is to archive the messages first, then roll through the > message bodies from the database (instead of parsing throughbt that > huge mail archive file) and archiving the tips into a second > database. This will also allow us to relate the tips, messages, and > author records to each other (which is a very cool thing).. > > The process runs fine against a sample file and then bombs against > the full archive. It's something I have been working on > incrementally and have been planning on finishing; I will put some > time into it today and let you know where it stands this evening. > Should give me a little time to fully evaluate the situation. > > Coolio?