this is only to specify inboxes, local deluvery adds the repository name
based upon the username.
sent is not invalid, but any repository must have a name as well as a table
name.
If you want to archive mail in inboxes you should use appropriat matchers
and mailets or write a new mailet to sort it out for you.
e.g.
<mailet match="[EMAIL PROTECTED]" class="ToRepository">
<repositoryPath> db://maildb/sent/timo</repositoryPath>
<passThrough>true</passThrough>
</mailet>
> -----Original Message-----
> From: Timo Nentwig [mailto:[EMAIL PROTECTED]
> Sent: 11 August 2003 14:48
> To: James Users List
> Subject: RE: Write sent mail to db
>
>
> The following message was sent by "Noel J. Bergman"
> <[EMAIL PROTECTED]> on Sun, 10 Aug 2003 15:21:40 -0400.
>
> > Perhaps there is a patch to the code that would provide a
> better diagnostic
> > message for mis-configured URLs.
>
> <!-- Alternative inbox repository definition for DB use. -->
> <!-- The format for the destinationURL is
> "db://<data-source>/<table>" -->
> <!-- <data-source> is the datasource name set up in the
> database-connections block, below -->
> <!-- <table> is the name of the table to store user inboxes in -->
> <!-- The user name is used as <repositoryName> for this
> repository config. -->
>
> <inboxRepository>
> <repository destinationURL="db://maildb/inbox/" type="MAIL"/>
> </inboxRepository>
>
> 1) Why is sent/ invalid when inbox/ is not?
> 2) I suggest that repositoryNname always is the user name for
> "mis-configured" URLs.
>
> ---------------------------------------------------------------------
> 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]
