Marcel,
> > http://issues.apache.org/jira/browse/JAMES-444
> What about have the feature configurable:
> onExpires=off // default
> onExpires=drop // discard expired mail without notice (my patch)
> onExpires=bounce // or other actions??
If we were to introduce this into RemoteDelivery, it would be necessary only
because RemoteDelivery does its own internal queuing.
If you have not seen the discussion on server-dev@ for a new approach to
spooling, you may want to read the thread starting with Message-ID:
<[EMAIL PROTECTED]> in the archives. In brief,
part of that proposal includes moving rescheduling outside of the mailets
and to the processor boundary, allowing us more flexibility on what to
reschedule.
As a nearer-term thing, even in the absence of the additional work required
to change the spool store and wrap processors into transactions, if we can
allow you to have something like:
<processor name="RemoteDelivery">
<schedule>
...
</schedule>
<mailet match="Expired" class="[Null|Bounce|...]"
</mailet>
<mailet class="RemoteDelivery">
</mailet>
</processor>
would that satisfy your requirements?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
