Robert.. this is realtively straight forward.. install a ToRepository
mailet and a matcher to filter *in* those mails you want archived.
Use PassThrough=true (check the correct syntax, this is *not* right!) if
you want your mail to be "tapped" (or copied into the archive)
The default (pass through=false) will store the mail and stop further
processing.
Place this mailet in a sensible place, at the start of "Transport" means
that all outgoing and incoming mail will be seen, but not errors or spam,
between local and remote delivery will only see outgoing.
Put local delivery into a new processor (use ToProcessor to direct the mail
to it) and add the archiving mailet there to only see incoming mail.
Or mess with the matcher you use.
You can use any of the repository formats, database, dbfile file or mdir
depending upon what suits you best.
Bear in mind that whilst James will religiously archive all matching mail
there is no provision for getting the mail out again, you need to use an
external tool.
Also bear in mind that mail is stored as received including all headers and
might not be readable without de-serialising/decoding/unencrypting or some
such.
A third alternative is to write your own mailet which will store mail in
the format of your choice.
If your format may be of interest to others, or useful for other repository
tasks you might want to consider writing a whole new repository. James is
modular like that, you can write your own "plug-ins" for more than just the
Mailet API should you have the inclination, up to and including adding
whole new protocols. So there should be little need to go outside James to
acomplish this.
d.
|---------+---------------------------->
| | Robert Buick |
| | <[EMAIL PROTECTED]|
| | om> |
| | |
| | 14/01/2004 01:31 |
| | PM |
| | Please respond to|
| | "James Users |
| | List" |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| 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]
***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s) only.
If you are not the intended recipient (or responsible for delivery of the message to
the intended recipient) please notify us immediately on 0141 306 2050 and delete the
message from your computer. You may not copy or forward it or use or disclose its
contents to any other person. As Internet communications are capable of data
corruption Student Loans Company Limited does not accept any responsibility for
changes made to this message after it was sent. For this reason it may be
inappropriate to rely on advice or opinions contained in an e-mail without obtaining
written confirmation of it. Neither Student Loans Company Limited or the sender
accepts any liability or responsibility for viruses as it is your responsibility to
scan attachments (if any). Opinions and views expressed in this e-mail are those of
the sender and may not reflect the opinions and views of The Student Loans Company
Limited.
This footnote also confirms that this email message has been swept for the presence of
computer viruses.
**************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
