Noel,
Thanks for your response.
> No. What database? The original proof of concept was done with a SQL
> script for testing. You can find it attached here:
>http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
pache.org&msgIdC5697
I am sorry, I meant VirtualUserTable table. What I am referring to is:
http://james.apache.org/FAQ.html#7 or
org.apache.james.transport.mailets.JDBCVirtualUserTable.java
I am trying to implement mail forwarding and as mentioned in my last
mail I have following records in VirtualUserTable
> > user:domain:target_address
> > User1:domain1:user[at]yahoo.com
> > User2:domain1:user[at]hotmail.com
and all mails for domain1 are going to user[at]yahoo.com
I am trying to experiment with this by changing the sqlquery that
org.apache.james.transport.mailets.JDBCVirtualUserTable.java uses. I
guess I can change the query by specifying it inside the <sqlquery> tag
but it doesn't seem to work. How can I correct this?
> Not quite. You want a separate quota matcher that understands your
> database. FixedQuota is intended to be a single quota. We will have
a
> per-user quota matcher after we add attributes to the user record.
In which release are we planning this functionality?
Thanks again for your help.
Regards,
Amit.
> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 05, 2003 12:28 AM
> To: James Users List
> Subject: RE: VirtualUserTable and quota
>
> > Regarding "JDBCVirtualUserTable" mailet:
>
> > User1:domain1:user[at]yahoo.com
> > User2:domain1:user[at]hotmail.com
>
> > All the mails that I send for domain1 are going to
user[at]yahoo.com,
> > is this the expected behavior?
>
> No. What database? The original proof of concept was done with a SQL
> script for testing. You can find it attached here:
>
>
>
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
ac
> he
> .org&msgIdC5697
>
> > Question about per-user quota:
>
> > if I want to implement a per user quota then I should change
> > "RecipientIsOverFixedQuota" to get the quota from the DB instead of
> > config.xml. Is that the right approach?
>
> Not quite. You want a separate quota matcher that understands your
> database. FixedQuota is intended to be a single quota. We will have
a
> per-user quota matcher after we add attributes to the user record.
>
> --- Noel
>
>
> ---------------------------------------------------------------------
> 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]
