Diego Castillo wrote:
last_updated is updated with every write operation, so that wouldn't be accurate. You'll want to parse the Received: header on the MimeMessage to see when it arrived. They have a relatively standard format and hopefully you can deduce which is the most recent.Noel,Thank you for the precise information. The JDBC spool does indeed implement the FIFO behaviour that I require. Maybe you can offer quick answers to some more questions: 1. How can a mailet retrieve the arrival timestamp of a mail? I guess this information is contained in column "last_updated" of table "spool", but I don't know how often it is overwritten.
I'm actually in the final stages of testing this on HEAD... switching from my hack mordred DB pool to DBCP, exposing a DataSource via JNDI, and changing all mailets and other database components to use this.2. My mailet uses MySQL for storing data. Can it benefit from the James' DataSource handling? I am thinking in adding my DataSource configuration to the James config file and get a reference to the object from within my mailet.
There is no real way to get info on the size of the spools. That's an interesting requirement, and it might be something worth exposing. Especially if we enforce FIFO (which I can't see why not), you could tell a management app that the ETD for a mail message is in "5 minutes" (like calling customer support). Would be interesting, but I think it'd be outside the scope of the mailet API and just a feature of James.3. How can my mailet find out the size of the spool and the outgoing repositories?
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
