I you're thinking along the right lines.. what you need to do is to mimic
the behaviour of the spam or error processors but in the transport or root
processor.
so something like this placed at the top of a block, or before a mailet, ..
<mailet match="All" class="ToRepository">
<repositoryPath>db://maildb/archive/sentitems</repositoryPath>
<passThrough> true </passThrough>
</mailet>
.. will archive all the mails that reach that point in the processor to the
"archive" table with the repository field set to "sentitems"
it is important that this have passThrough set to true in order that the
following mailet recieves the message for processing.
you may also have to meddle with the organisation of the processors, and/or
change the matcher on the archive settings (and use more than one archiver)
if you want to archive local delivery and remote delivery seperately.
d.
> -----Original Message-----
> From: Rizwan Ahmed [mailto:[EMAIL PROTECTED]]
> Sent: 07 April 2002 10:35
> To: James Users List
> Subject: how to store messages permenantly in a db??
>
>
>
> Hello Group
>
> How will I configure my cong.xml to store all (incoming) messages
> regardless
> of repositories or spool files.
>
> I was just able to connect james with mysql and it creates
> repository tables
> where the message doesn't stay permenantly. My objective was to
> have a table
> that stores all incoming messages for all users permenantly.
>
> I tried to tweak config.xml but it ends in james not starting...
>
> Thanks for any help
>
> Regards
> Rizwan
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
