Personally, what we did (I wrote a commerical list manager using James) is to use the matcher/mailet combo and use the mailet to write the mail into a table of your own choosing. At least then you will have full control over what get's written where (an how). If you use this method you will not need to set up an inbox for each email address you want to store.
-- Jason > -----Original Message----- > From: Robert Buick [mailto:[EMAIL PROTECTED] > Sent: 14 January 2004 13:32 > To: [EMAIL PROTECTED] > Subject: email archive > > > Hi, > I've built James from the CVS repository (it runs up as > 3.0a1) and use > postgreSQL 7.3.4 on RH9. > I would lke to be able to archive incoming email messages so > that I can > subsequently run tests/queries/campaigns etc. > My question is, what would you suggest is the most > appropriate method of > archiving? using database triggers on the inbox table or could it be > to develop matcher/mailet to archive to the database? > > Thanks for your time and help, > > Rob Buick > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
