Good point. I can see how different users would have different quotas. Ok, so if we change (I don't want to call it extend as that implies some OO stuff) JamesUser to support quotas, how do you configure (e.g., a default) and manage that? -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/
Noel J. Bergman wrote: >>I might tweak the matcher to look like this though... >><mailet matcher="UserOverQuota=6m" class="ToProcessor"> > > > I disagree on the grounds that we extend JamesUser to include a quota > property. This means that the matcher would check each user's quota, and > reject each one for which that message would create the over quota > condition. > > That is why there was no parameter to the matcher, although there could be a > default for when the user's quota is not explicitly set. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
