As previously suggested on this list, I added a mailet in my transport match that stores all messages in a JDBC repository and continues with processing, thus creating a cool mail archive.

So I fired up Cocoon, wrote a couple of xsp pages, and I can now browser the mails. Cool :-)

Then I said, "ok, let's do some searches with JDBC"... and I found out (stupid me not to look before) that the mail is totally in a blob.
Thus I cannot easily show or search subjects of the mails, because they are in the blob. The same with attachementsVScontent, but this is minor.

Is this a design decision? Ie is there a reason why the whole mail is kept in a blob instead of externalizing the most common mail headers, like

Return-Path:
Received:
Message-ID:
Subject:
Mime-Version:
Content-Type:
X-Mailer:

and also have a separate table with all the attachements separated in different fields?

If this is what the repository will remain in the future, any suggestion on what I should do to make it easily searchable? Should I make it add these columns, or is there a better alternative?

Thanks a lot guys, James really ROCKS!

We used Notes before, and guess what, my mail admin has fallen in love with James after a couple of days. How sweet :->

--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to